SCORM
A SCORM wrapper is JavaScript library that serves as an abstraction layer between the SCORM API and your course. If you’ve ever used jQuery, you can think of a SCORM wrapper’s relationship to the SCORM API as being very similar to jQuery’s relationship with a web browser’
e-learning
Made a minor update: scorm.quit() was setting a value (cmi.exit) but not invoking scorm.save() prior to termination. This could lead to failure to persist the value of cmi.exit in the LMS. View the latest update on GitHub Comments Bard Dale wrote on March 4, 2014 at
best practices
In part one of this series, we published a simple Captivate course and examined its file structure. In part two, we cleaned up the HTML file and externalized all JavaScript. In part three, we cleaned up the JavaScript. In this installment, we will examine and update the SCORM code. Captivate
e-learning
Update 10/13/2011: I added more comments to the ActionScript code to help explain what each line of code does. I also added a Flash CS4 version of the FLA to the ZIP so more people can access the example. My “Planets” example (How to Add Basic SCORM Code
e-learning
The pipwerks SCORM Wrapper has been updated with a small patch for handling odd behavior in the Plateau LMS. Special thanks to Joe Venditti for the patch (and sorry for taking almost 2 years to add it to the codebase!). Get the latest version here. Comments Bobby wrote on August
e-learning
An abstraction layer is a way of hiding complexities and maintaining cleanliness in your application. For example, if you want to save a file in your word processing application, you simply click “save”, while a whole host of actions is performed for you under-the-hood. In this example, you’re shielded
SCORM
SCORM courses use JavaScript to send data to the LMS. This data then sits in the browser until the LMS writes it to the database (usually via AJAX or form posts). As previously discussed, invoking commit (save) will ensure the LMS actually writes this data to a database. But what
e-learning
A number of people have recently asked me about the scorm.save() function in the pipwerks SCORM wrappers. What is it, and when should it be used? The pipwerks scorm.save() function is a shortcut for SCORM’s Commit (SCORM 2004) and LMSCommit (SCORM 1.2) methods. Invoking commit in
ramblings
As you may have read in previous posts or tweets, I’m working on a new SCORM 2004 wrapper for both JavaScript and ActionScript that will contain advanced functionality and improved shortcuts. For instance, I’m trying to write an easier way to work with the cmi.interactions model, and
Tips and Tricks
I recently emailed a shortlist of good SCORM development resources to a colleague, and figured I should probably post a list here, too. This is a quickie list, and I’m sure I’m leaving someone out. If you know of any resources I’ve missed, please add a link
ramblings
Most e-learning developers don’t care about SCORM and only (begrudingly) learn enough to get the job done. I don’t blame them. The other day I was reading some old Drupal community posts (circa 2005) about adding SCORM functionality to Drupal. One comment stood out: SCORM was the big
e-learning
I’ve had a number of people ask me about extending my SCORM helpers (the JavaScript-based SCORM API wrapper and the two ActionScript classes) in order to completely remove the need to know any of the “cmi” calls. For instance, being able to do something like this: scorm.bookmark = "