SCORM actionscript class
Actually, I have two updates to report: SCORM API Wrapper updated to version 1.1.4 I’ve received a number of emails from folks who say their LMS can’t auto-detect the API. Therefore, by popular demand, the SCORM API Wrapper for JavaScript has a new feature: the ability
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
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
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
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!
ActionScript
Found a small bug when using the wrapper with Flash (AS2): functions that return string values (such as SCORM.data.get()) were coming out ‘undefined’. (grr) Explicitly typing the return value as a string seems to make Flash happy. return String(value); This all-in-one wrapper has now been tested successfully
e-learning
Some small edits to the wrapper: 1. Fixed a few typos in debug statements 2. Added extra error-checking during SCORM.connection.initialize; if connection cannot be made AND no error code is given, display notice that server has not responded. Related links: * Original SCORM API Wrapper journal entry * pipwerks.com
e-learning
I’ve been a longtime user of the ADL wrapper (with code from the late Claude Ostyn), and to be honest, it’s pretty much met my needs. But I was never completely comfortable with the wrapper for two reasons: 1) The code is hard to read with confusing and