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
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
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
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
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