e-learning
I’ve had a number of people ask me about extending my SCORM helpers (the JavaScript-based SCORM API wrapper and the two ActionScript classes) in order to completely remove the need to know any of the “cmi” calls. For instance, being able to do something like this: scorm.bookmark = "
ActionScript
There is a newer list of variables available, which includes new Captivate 4 variables. A recent post (link no longer available) in the elearning development forum (link no longer available) reminded me that I forgot to post some unpublished Captivate variables I dug up a while back. These were gathered
e-learning
Ok, I just had to write a quick blurb about this one: in about 3.5 years of using SCORM in my own course code, I had never used cmi.core.exit (SCORM 1.2) or cmi.exit (SCORM 2004). Seems incredibly daft of me now that I’ve taken
Tutorials
In my previous post, I briefly explained how to add SCORM code to an existing Flash file by using the pipwerks SCORM wrapper and SCORM ActionScript class. Today, I’m going to explain how to add SCORM code to a plain HTML file. This example uses SCORM 1.2 syntax,
SCORM actionscript class
Update 10/2011: The Planets example has been updated (almost completely rewritten) and no longer strictly adheres to the steps and screenshots in this tutorial. The general concepts are the same, but the project files have been substantially refined. To prevent confusion about which files to use, I have removed
Adobe Captivate
Many of us use a Flash-based course interface (a.k.a. ‘player’) to load Captivate SWFs and other content. A well-known stumbling block for this kind of ‘loaded SWF’ approach has been Captivate’s lack of ActionScript support — Captivate won’t allow a user to add a simple line of
ActionScript
A few months ago I wrote about the dilemma of trying to load Captivate SWFs into an ActionScript 3-based parent SWF. Dilemma solved! I present to you the ActionScript 3 class LegacyCaptivateLoader. This class utilizes ExternalInterface and a proxy SWF to facilitate sending commands to and querying data from an
CSS
Clive Shepherd recently wrote about “inductive learning.” He said: In my post last week, Whatever happened to inductive learning?, I complained how difficult it was with current rapid development tools to write more conversational inductive questions in which you as author are able to comment on each selection that the
e-learning
I read not one, but three great blog posts today regarding what kinds of questions you should asking yourself when working on a project. Two of the blogs were not specific to the e-learning industry, but they apply nonetheless. Why? The first blog, by Jason at 37signals.com, suggests that
Adobe Captivate
You may be familiar with the famous “Captivate variables” (see page 201 in PDF link), but did you know about “rdcmndHidePlaybar”? It isn’t mentioned by Adobe in their documentation, but it’s a handy one to know about. You can toggle the Captivate playbar’s visibility by importing two
accessibility
Adobe has a short but useful article detailing how to make your Adobe Captivate movies more accessible. These are pretty simple (borderline “no-brainer”) steps a Captivate author can easily implement: * Add a description to an Adobe Captivate movie * Add a description to an individual slide * Limit quiz questions to multiple
ActionScript
Here’s a simple example of how the SCORM AS3 class can be utilized. (This example uses SCORM 2004 calls.) import pipwerks.SCORM; import flash.external.ExternalInterface; //Declare variables var success:Boolean = false, completion_status:String; //Initialize a new SCORM object! var scorm:SCORM = new SCORM(); //Initialize SCORM connection success