Two small but important edits.
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.
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
Most e-learning tools do not promote the creation of effective courses, web standards, or accessibility; they merely make cookie-cutter course development easier for technically inexperienced course developers.
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.
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.
Folks, it’s simple — if you have to paste a “this site works best with XXX browser” message on your site, whether it’s an LMS, an online course, or just a website for your mom’s knitting club, you’re doing something wrong. Do us a favor and stop it.
Today was the day… I gave a presentation at the eLearning Guild’s DevLearn 2007 conference in San Jose. Topic? Captivate-to-Flash ActionScript Communication.