LegacyCaptivateLoader: Dealing with pre-existing scripts in your Captivate SWF

3 Comments

When I designed the LegacyCaptivateLoader, I was focused on giving the ActionScript 3 SWF the ability to control the ActionScript 2-based Captivate SWF; I hadn’t given much thought to how the situation affects Captivate SWFs using one of the workarounds I just described. Can the embedded SWFs still work? Will JavaScript calls from Captivate still work with ActionScript 3’s ExternalInterface system? The short answer is yes, but it may take some tweaking on your part.

SCORM wrapper updates (JavaScript and ActionScript)

JavaScript SCORM_API_Wrapper.js now at v1.1.3. Includes important typo correction.

SCORM.as classes (AS2 & AS3) now at v1.01. Includes check for ExternalInterface availability and presence of required pipwerks JavaScript wrapper.

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

9 Comments

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.