SCORM actionscript class
Update 10/2011: The Planets example has been updated (almost completely rewritten) and no longer strictly adheres to the steps and screenshots in this tutorial. The general concepts are the same, but the project files have been substantially refined. To prevent confusion about which files to use, I have removed
Project Updates
Here’s a bunch of news updates regarding the pipwerks SCORM JavaScript wrapper. Time for class? A big fad these days is object-oriented JavaScript; libraries such as jQuery and MooTools make it really easy to create JavaScript “classes” (in quotes because from what I can gather, they’re really JavaScript
Adobe Captivate
Many of us use a Flash-based course interface (a.k.a. ‘player’) to load Captivate SWFs and other content. A well-known stumbling block for this kind of ‘loaded SWF’ approach has been Captivate’s lack of ActionScript support — Captivate won’t allow a user to add a simple line of
ActionScript
A few months ago I wrote about the dilemma of trying to load Captivate SWFs into an ActionScript 3-based parent SWF. Dilemma solved! I present to you the ActionScript 3 class LegacyCaptivateLoader. This class utilizes ExternalInterface and a proxy SWF to facilitate sending commands to and querying data from an
CSS
Clive Shepherd recently wrote about “inductive learning.” He said: In my post last week, Whatever happened to inductive learning?, I complained how difficult it was with current rapid development tools to write more conversational inductive questions in which you as author are able to comment on each selection that the
SCORM actionscript class
Actually, I have two updates to report: SCORM API Wrapper updated to version 1.1.4 I’ve received a number of emails from folks who say their LMS can’t auto-detect the API. Therefore, by popular demand, the SCORM API Wrapper for JavaScript has a new feature: the ability
Project Updates
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
changelog
Small but important edits: * Added snippet of code to double-check API connection is active before returning a ‘true’ boolean value. * Fixed a typo for evaluating whether an error code has been returned from the LMS Also added some code from the Firebug folks that allows Firebug’s “console” functions to
ActionScript
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. return String(value); This all-in-one wrapper has now been tested successfully
e-learning
Some small edits to the wrapper: 1. Fixed a few typos in debug statements 2. 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
e-learning
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
ramblings
I just got Captivate 3, and eagerly installed it to see if any improvements have been made regarding JavaScript and ActionScript handling. Short answer: nope. JavaScript According to Captivate’s ‘Help’: You can add JavaScript to click boxes, text entry boxes, and buttons in Adobe Captivate projects. The JavaScript can