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 = "
There is a newer list of variables available, which includes new Captivate 4 variables. A recent post (link no longer available) in the elearning development forum (link no longer available) reminded me that I forgot to post some unpublished Captivate variables I dug up a while back. These were gathered
The SCORM API wrapper (v1.1.7) has been updated to automatically set the initial course status and the exit status. The point of my SCORM API wrapper is to make working with SCORM easier. These two new functions are intended to ensure you follow best practices with your SCORM
Ok, I just had to write a quick blurb about this one: in about 3.5 years of using SCORM in my own course code, I had never used cmi.core.exit (SCORM 1.2) or cmi.exit (SCORM 2004). Seems incredibly daft of me now that I’ve taken
In my previous post, I briefly explained how to add SCORM code to an existing Flash file by using the pipwerks SCORM wrapper and SCORM ActionScript class. Today, I’m going to explain how to add SCORM code to a plain HTML file. This example uses SCORM 1.2 syntax,