Friday, March 8, 2013

Mobile Development Options - Part 3: Mobile Web Development with Dreamweaver

By Mark Giglione


Mobile Development Options - Part 3: Mobile Web Development with Dreamweaver


Adobe Dreamweaver versions CS5.x thru CS6.x provide tools for creating and editing web sites targeted for mobile devices.  A mobile web site is styled and behaves as if it were a native mobile application but is actually a web site that can be viewed on different mobile devices. A mobile web site does not need to be downloaded but is viewable across mobile device platforms using each device’s mobile web browser.  

As an additional option, a standalone native mobile device ‘app’ (typically targeted for iOS or Android) can be created with Dreamweaver by embedding a mobile web site (or a mobile web application) within a pre-created “native code” wrapper which is then compiled into a native application.  The compiled application can then be deployed using a channel such as iTunes or the Android marketplace.  

A major advantage of building a web site or web application optimized for mobile devices is that development is accomplished using HTML, Javascript and CSS rather than with a compiled native code language such as Objective-C or Java.  While not required, typically a mobile web browser optimized Javascript library is used to simplify the creation of the Graphical User Interface (GUI) elements and behaviors.  While there are limitations to this approach compared to natively coded applications, web tool based development is quite suitable for a wide range of projects and may be easier to master for novice mobile developers.

Dreamweaver currently supports jQuery Mobile and PhoneGap directly (though PhoneGap will work with other mobile Javascript libraries as well).  jQuery Mobile is a Javascript framework for developing mobile device optimized web applications and web sites. PhoneGap works by embedding a mobile web application (which can be built with jQuery Mobile) in a native (PhoneGap API supporting) project shell tailored for each target mobile platform. The latest versions of Adobe Dreamweaver provide integrated tools that can be used to create jQuery Mobile and/or PhoneGap based projects. However, both PhoneGap and jQuery Mobile are Open Source and can be used independently of Dreamweaver.  

Getting started with jQuery Mobile and Adobe Dreamweaver CS5.5
http://www.adobe.com/newsletters/inspire/may2011/articles/article4/index.html?trackingid=IOZGV

Building a mobile app with PhoneGap and Dreamweaver (7 part series)
http://www.adobe.com/devnet/dreamweaver/articles/phonegap-mobile-app-pt1.html   

Build mobile apps and websites with Dreamweaver (CS5.5)
http://www.adobe.com/devnet/dreamweaver/dreamweaver-mobile.html

Enhanced jQuery mobile support (CS6)
http://tv.adobe.com/watch/learn-dreamweaver-cs6/enhanced-jquery-mobile-support/

PhoneGap
http://phonegap.com/

jQuery Mobile
http://jquerymobile.com/

Scripting the Web - Part 1: Introduction to JavaScript
http://www.adobe.com/devnet/dreamweaver/articles/introduction-to-javascript.html

Scripting the Web - Part 2: Introduction to jQuery
http://www.adobe.com/devnet/dreamweaver/articles/introduction-to-jquery.html

Thursday, February 14, 2013

What's in a deadline... online

by Alan Regan

So, When's This Thing REALLY Due?

Thoughts on deadlines in online testing with timed tests


Within our learning management system, Courses (powered by Sakai), there is a powerful testing tool called Tests & Quizzes.  This tool can accomplish many assessment goals, from surveying opinions to conducting high-stakes final examinations.  If you want students to take a low- or high-stakes test online, one of the most important questions to ask is: when is it REALLY due?

Why is this important? In a purely online setting, you need to decide whether the due date is for completing an assessment or starting an assessment. In other words, must a student submit before the due date or must he/she at least begin the assessment before the due date?  This is critical when we think about timed assessments online.

For example, let's say you want students to take a one-hour test. The due date is Friday at 5:00 PM. In the "submit by" model, this means that students must start the test by 4:00 PM to have a full hour. However, if they start at 4:58 PM, the internal timer and likely the assessment description will still say it's a one-hour test, but in reality they only have two minutes left. This can create confusion.

The other approach is to treat the due date as a "start by" date. This way, a deadline communicated as a "start by" date would offer students the full time to complete the assessment as long as they start by that date.  We'll review how to accomplish both models.



"SUBMIT BY" MODEL


This is the traditional model of a deadline. In a classroom setting, there's a lot of structure. The class begins at a specific time and ends at a specific time. The deadline is usually by the end of the class and students must physically turn in their papers before the next class begins.  In an online setting, the beginning and ending dates can be fixed or more fluid. The "open" testing period may be two days, while the exam itself may be an hour-long timed assessment, for example. This interpretation of the start and end date/time is where student confusion can happen.

The "submit by" model says that the "due" date is the deadline. This approach can teach students the importance of time management and personal accountability. Students will experience pain when they misinterpret or ignore directions. Some of their work may be lost by not saving or submitting work before the deadline. Professors that choose this approach should be prepared for complaints, especially at the outset. Offering a low-stakes or no-stakes practice exam is strongly recommended to reduce student and professor frustration when using this approach.

To accomplish a "submit by" deadline, we recommend the following settings:
  • Under "Assessment Introduction," clearly communicate that this is a "submit by" deadline. In the Description/Intro field, describe the assessment and be explicit in the settings and expectations. If the deadline is 5:00 PM, it does not hurt to explain that students must begin the assessment no later than 3:55 PM to receive the full time -- students that start after that time must complete the assessment by 5:00 PM despite any time listed on the countdown timer. You can click "Show/Hide Rich-Text Editor" to add emphasis and color to highlight key points. We pad the date by five minute to account for potential time differences between student clocks and the server's clock; the assessment is controlled by the server's clock.
  • Under "Delivery Dates" in the assessment's settings, enter the deadline in the Due Date field (e.g. 03/15/2014 05:00:00 PM).
  • Under "Delivery Dates," enter the same date plus five minutes in the Retract Date field (e.g. 03/15/2014 05:05:00 PM). 
  • Under "Timed Assessment," enter the one hour limit.
  • Under "Assessment Organization," we strongly recommend that you select "Each Question is on a separate Web page" in the Question Layout section. This will insure that student work is saved after they complete each question.
  • Under "Submissions" in the settings, select the option "Late submissions WILL NOT be accepted after the due date" in the Late Handling section.
  • Under "Submissions," check the box for "Saved assessments will be automatically submitted after the retract date passes" in the Automatic Submission section.
  • Under "Feedback," we recommend the option "Feedback will be displayed to the student at a specific date" if you want to release automated scores and feedback. This way, you can set a date after the deadline and not expose answers to students when others haven't completed the assessment yet. If there will be make-up test takers, you may want to set the date several days after the deadline to allow for these make up exams. (For make-up tests, you would create a group for those specific test takers, duplicate the assessment, and release that copy to only that specific group.)
  • For other setting details, refer to our Tests & Quizzes Settings guide.
  • Always save the settings and review them thoroughly before publishing the assessment. 

"START BY" MODEL


In this model, we've decided that the "due date" is the time students must at least begin the assessment. If they start by the due date on a timed test, then they'll have the full amount of time before the retract date to turn in their assessment. You still run the risk of student complaints, but you minimize the risk by setting a time that will align with the assessment's built-in timer.

To accomplish a "start by" deadline, we recommend the following settings:
  • Under "Assessment Introduction," clearly communicate that this is a "start by" deadline.
  • Under "Delivery Dates" in the assessment's settings, enter the deadline in the Due Date field (e.g. 03/15/2014 05:00:00 PM).
  • Under "Delivery Dates," enter the REAL deadline in Retract Date field (e.g. 03/15/2014 06:05:00 PM). We pad the date by five minute to account for potential time differences between student clocks and the server's clock; the assessment is controlled by the server's clock.
  • Under "Timed Assessment," enter the one hour limit.
  • Under "Assessment Organization," we strongly recommend that you select "Each Question is on a separate Web page" in the Question Layout section. This will insure that student work is saved after they complete each question.
  • Under "Submissions" in the settings, select the option "Late submissions WILL be accepted after the due date. However, this applies only to students who have not submitted their work prior to the due date. They will be given one chance to do so and their submission will be tagged as late." 
  • Under "Submissions," check the box for "Saved assessments will be automatically submitted after the retract date passes" in the Automatic Submission section.
  • Under "Feedback," we recommend the option "Feedback will be displayed to the student at a specific date" if you want to release automated scores and feedback. This way, you can set a date after the deadline and not expose answers to students when others haven't completed the assessment yet. If there will be make-up test takers, you may want to set the date several days after the deadline to allow for these make up exams. (For make-up tests, you would create a group for those specific test takers, duplicate the assessment, and release that copy to only that specific group.)
  • For other setting details, refer to our Tests & Quizzes Settings guide.
  • Always save the settings and review them thoroughly before publishing the assessment.

OTHER ONLINE TESTING TIPS

  • Remind students that essay or file upload questions are not auto-graded. Students may panic when they see the initial grade before you've reviewed and assigned grades for manual grading items. Prepare them ahead of time.
  • If you use essay questions, please remind students to save their work regularly. We recommend that students draft their essay in Microsoft Word or another word processor and paste in their work. Students can lose their work if they: (A) fail to save their work often by clicking the "Save" button on the page (especially if time runs out on a timed assessment!), (B) accidentally close their web browser tab or window, (C) click the browser's Back button, (D) accidentally Select All and erase their content, or many other situations. This is why it's their responsibility to save their work regularly.

RESOURCES

  • Pepperdine's Test & Quizzes documentation
  • Clicking the blue question mark (?) icon in Courses will pull up contextual help. The Tests & Quizzes documentation is an excellent resource.



Friday, January 18, 2013

Converting From Passive to Active Learning

by Hong Kha

Converting From Passive to Active Learning




This week we'll be discussing best practices for converting your lessons for online learning.

The process of converting your classroom activities for online learning should be more thought out than just taking what you do in the classroom and doing it online. Faculty who are new to teaching online often make initial attempts of converting lessons for their new teaching environment by moving an in-classroom discussion to an online discussion forum after giving a reading assignment. Or they opt to create a video lecture of what they would normally deliver to a room full of students and assign a discussion topic after watching the video. While these types of activities can give you an idea of how well your students understand the content, it may not be a process that will help your students retain the information because it isn't engaging enough.

Here are some handouts to help you identify what you're doing now that works well in the classroom and what can be converted for online activities and the tools that can be used to do it.


Database Tech Tools

Flip Teaching 101

Friday, January 11, 2013

Mobile Development Options - Part 2: MIT App Inventor

by Mark Giglione

Mobile Development Options - Part 2: MIT App Inventor

MIT App Inventor is a web based, visual programming environment for creating Android apps.  App Inventor’s Integrated Development Environment (IDE) is web based with a graphical user interface. Application programming is accomplished by stacking and connecting graphical building block components, reminiscent of jigsaw puzzle pieces.

App Inventor was originally developed by Google but the project is now maintained by the Massachusetts Institute of Technology (MIT). The intent of the App Inventor project is to provide an environment in which non-technical users can learn application development concepts without initially learning a formal programming language. The initial target audience was high school and college students but the software is open source and free to use by any interested party.

App Inventor is also representative of a class of web based, graphical development environments for building both Android and iOS applications. Many of these environments are commercial; typically the commercial services have a low entry cost initially but subsequently additional services for developing and publishing applications may need to be purchased. However, these services are broadly similar in concept to the MIT App Inventor and App Inventor can provide a “free” introduction for exploring and evaluating this type of mobile app development environment.

MIT App Inventor
http://appinventor.mit.edu/

Wikipedia: App Inventor for Android
http://en.wikipedia.org/wiki/App_inventor

Monday, December 17, 2012

Midnight Assignments - How do you set the date and time?

by Alan Regan

"I have an assignment due at midnight. How do I enter the date and time?"


This tip comes from one of our professors, Dr. Chris Heard of Seaver College's Religion Division.  Dr. Heard had an assignment due at midnight and he wasn't sure how to record the time.  Does he record the time as 24:00:00 (PM) on the day the assignment is due or 00:00:00 (AM) the next day?

Let's say that you want to have students submit an assignment by midnight on Tuesday, June 18, 2013.  You would set the due date to Wednesday, June 19, 2013 at 00:00:00 AM.

Courses (powered by Sakai) will not accept 24:00:00 PM as a valid date.  The correct option for midnight is 12:00 AM the following day or 00:00:00 in military time.

Several other professors have chosen to simply set the deadline to 11:59:59 PM the day of the due assignment as another workaround.

Example 1: Activity is due at midnight on Tuesday, June 18, 2013 (they have all day Tuesday to complete the activity)
  • Assignments: Jun 19 2013 12:00 AM
  • Forums: 6/19/2013 12:00 AM
  • Tests & Quizzes: 06/19/2013 00:00:00 AM
Example 2: Activity is due at noon on Tuesday, June 18, 2013 (they have until midday Tuesday to complete the activity)
  • Assignments: Jun 18 2013 12:00 PM
  • Forums: 6/18/2013 12:00 PM
  • Tests & Quizzes:  06/18/2013 12:00:00 PM

We hope this "time" tip helps you in future assignments!

Friday, December 14, 2012

Mobile Development Options - Part 1: Overview

By Mark Giglione

Mobile Development Options - Part 1: Overview

This series will provide brief introductions to options for mobile app development with links to pursue each topic in more depth. The general plan is to begin with technologies that do not require a background in programming (or otherwise require traditional programming skills) and then explore options that progressively involve acquiring more technical expertise.

Part 1: Overview
Part 2: MIT App Inventor
Part 3: Mobile Web Development with Dreamweaver
Part 4: Titanium Appcelerator & Titanium Studio
Part 5: Processing
Part 6: Xcode for Apple iOS Development
Part 7: Eclipse for Android Development
Part 8: Other Tools and Wrap-Up


Overview

There are two primary strategy choices for creating mobile applications. The first is to create a ‘native’ application targeted for a specific device or device operating system (e.g. iOS devices, such as an iPad or iPhone, and Android devices like the Amazon Kindle). The second is to develop a website or web application that is designed for viewing by a mobile device.  

A native application is tailored and optimized for use on a specific device and is usually distributed through an online marketplace (for example  iTunes for iOS devices). Typically a native application requires the use of a traditional computer programming environment such as Xcode or Eclipse (but alternative development approaches are available).  

Mobile websites and mobile web applications can have a similar look and interface conventions as a native mobile application but are created using the tools and technologies that are typically used to create conventional web sites (e. g. HTML, CSS and Javascript). This has the advantage of utilizing tools that may already be familiar from previous web development work and the web based application is directly accessible from the web without first being downloaded and installed. While a native application may be a better choice where performance or device specific features are required, mobile web applications can be quite suitable for implementing simple to moderately complex applications. Mobile web applications are for the most part inherently “cross platform” since they are web rather than device based. Additionally, many mobile web applications can also be packaged and distributed as a standalone native applications.

The next installment will discuss the open source MIT App Inventor tool which uses codeless “visual” programming for creating native Android applications. App Inventor is also representative of a class of mobile development tools where the development environment is web based (rather than running on the desktop) but the final product is a native application.

Thursday, December 6, 2012

Get Citations Right Through Pepperdine Libraries Search

by Alan Regan

Citing Made Easy: Leverage Pepperdine Libraries Search


You've asked your students to write a research paper but their citations are incorrect or consistent. In addition to pointing them to Pepperdine Libraries' valuable research tips, you can also point them to a solution that has likely been staring them in the face.

To find books and articles on a desired research topic, your class is hopefully taking advantage of the many physical and digital resources offered by our Pepperdine Libraries.  These materials are available through a powerful, central search tool, powered by WorldCat.  In addition to finding these resources, the tool will also provide the correct citation based on several common formats.

Instructions:

  1. Visit http://library.pepperdine.edu.
  2. Enter your search term or book title in the main search box.

  3. Click the title of a search result.
  4. Click "Cite/Export" in the options near the top right, next to "Print" and "Email."
  5. Click the desired format, e.g. APA, Chicago, Harvard, MLA, and Turabian.
  6. Copy the full citation.

It's that easy to find the correct citation for a book, article, or other resource.