Really simple SCORM AS3 wrapper example
Here’s a simple example of how the SCORM AS3 class can be utilized. (This example uses SCORM 2004 calls.)
Here’s a simple example of how the SCORM AS3 class can be utilized. (This example uses SCORM 2004 calls.)
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.
JavaScript SCORM_API_Wrapper.js now at v1.1.3. Includes important typo correction.
SCORM.as classes (AS2 & AS3) now at v1.01. Includes check for ExternalInterface availability and presence of required pipwerks JavaScript wrapper.
Proposing a community-defined set of simplified e-learning development standards that can be viewed more as ‘rules of thumb’ than law.
Two small but important edits.
I just converted my AS2 SCORM class to AS3.
I just finished an ActionScript 2.0 class file meant to be a companion to my JavaScript SCORM API wrapper. It includes a bunch of type checking, type conversion, and error-checking, and works with both SCORM 1.2 and 2004.
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.
Some small edits to the wrapper: Fixed a few typos in debug statements 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 SCORM page
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 overly complicated looking variable names, and 2) the code made heavy use of global variables, which in this Web 2.0 world is a big no-no. This past week I decided to roll up my sleeves and make a new SCORM API wrapper that takes care of these issues.