changelog
The pipwerks SCORM wrapper examples have been successfully tested in SumTotal TotalLMS 7.6. FYI, the examples’ imsmanifest.xml files required some modifications (the old manifests worked fine in the ADL test suites, but coughed a little when used in SumTotal TotalLMS 7.6). The JavaScript, ActionScript and HTML in
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
ActionScript
Finally got around to making some Flash files that demonstrate the pipwerks SCORM ActionScript classes. I’ve created examples for both AS2 and AS3. You can get them here. Both of these examples have been successfully tested using the latest ADL test suites for SCORM 1.2 and 2004. A
Project Updates
JavaScript SCORM_API_Wrapper.js now at v1.1.3 Changes: 1. Added SCORM.isAvailable() function; This allows Flash’s ExternalInterface to confirm the presence of the JavaScript wrapper before attempting any LMS communication. Parameters: none. Returns: Boolean (static, true). 2. Fixed an important typo: I had forgotten the empty
best practices
Understanding that we should be using standards and best practices throughout e-learning development, the question becomes “what standards and best practices should we follow?” Here’s my attempt at outlining some basics. Please feel free to suggest additional items in the comments section. Follow established “web” best practices. Separate presentation
ramblings
Question: Why don’t more e-learning developers use standards? I don’t know for sure, but I have a number of guesses. Here’s a quick list off the top of my head: * Lack of knowledge about standards * Confusing or obtuse documentation * Competing standards * Misconceptions about cost effectiveness * Difficulty / Lack
ramblings
Today Rapid Intake announced a new service named Unison. Not having used the service, I won’t pretend to know whether it’s a worthwhile service or not. It’s certainly an intriguing idea, and with its oft-mentioned low price, it’s guaranteed to get some industry buzz. Out of
e-learning
Today I’m working on a simple JavaScript/XML-based quiz. I decided I’d like to use a standardized XML format for the quiz questions and answers, so I googled QTI, a common quiz format. Turns out QTI is (yet another) IMS specification (duh, I should have known that!). I
changelog
Small but important edits: * Added snippet of code to double-check API connection is active before returning a ‘true’ boolean value. * Fixed a typo for evaluating whether an error code has been returned from the LMS Also added some code from the Firebug folks that allows Firebug’s “console” functions to
e-learning
I just converted my AS2 SCORM class to AS3. Read documentation and download file(s) here. Note this class requires the pipwerks SCORM API wrapper for JavaScript. Not being much of an AS3 guy (so far!), it was easier than I expected; I guess since I had already used strong
CSS
I just saw something interesting I thought I’d pass along. In the new HTML 5 proposal, the strong element is being modified to represent “importance rather than strong emphasis.” The WHATWG gives the following example: <strong>Warning.</strong> This dungeon is dangerous. <strong>
ActionScript
I just finished an ActionScript 2.0 class file meant to be a companion to my JavaScript SCORM API wrapper. Update: AS3 version now available, too. Simplified syntax The idea was simple: give me (and others) a way to make SCORM calls using ExternalInterface without having to constantly type ExternalInterface!