The IMS Global Learning Consortium needs to loosen up!

I looked up the QTI specs on the IMS site and couldn’t believe the boldfaced notice I saw on the page: “HTML documents may be viewed online, but may not be printed without permission” (emphasis added).

Can you believe that? IMS is in the business of creating standards they want the whole world to use. These standards should be open, easily accessible and free from licensing constraints. Why on earth do they want to put silly notices like this on their site?

SCORM API Wrapper updated to 1.1.1

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.

SCORM API Wrapper updated to v1.1

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

A revised SCORM API wrapper

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.

Loading Captivate files into an AS3 Flash SWF

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.