pipwerks

SCORM JavaScript wrapper 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

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

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

New: LegacyCaptivateLoader class

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

Captivate tip: Toggling the controller's visibility

You may be familiar with the famous “Captivate variables” (see page 201 in PDF link), but did you know about “rdcmndHidePlaybar”? It isn’t mentioned by Adobe in their documentation, but it’s a handy one to know about. You can toggle the Captivate playbar’s visibility by importing two

SCORM JavaScript wrapper updated to 1.1.4

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

pipwerks © 2026