By popular demand, the SCORM API Wrapper for JavaScript has a new feature: the ability to specify what version of the SCORM API should be used.
Also, I converted the AS2 demonstration FLA to Flash 8 format and posted it as a separate ZIP file.
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 the examples remain unchanged. If you’ve previously downloaded the examples, I suggest you download the updated versions to get the newer manifests. Of course, if you’re a pro at manifests (Aaron?), you could always make better ones… making the imsmanifest is my least favorite part of working with SCORM. As always, if you test these in your LMS, please let me know — even if it doesn’t work! Thanks 🙂
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.
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.
I researched the different methods available for AVM1 to AVM2 communication, and discovered there are a few workarounds that can enable the AS3 SWF to communicate with the AS2 SWF. I spent the entire day whipping up a Captivate-specific proof-of-concept.
