In part one of this series, we published a simple Captivate course and examined its file structure. In this part, we’ll take an in-depth look at the HTML generated by Captivate (using the SCORM 2004 publishing template) and clean it up as much as we can. Here’s the
Adobe Captivate is an enormously popular tool for e-learning developers. My assumption is that most Captivate users chose Captivate as their development tool because it enables them to publish LMS-compatible courses without requiring any programming skills — no need to know JavaScript, ActionScript, SCORM, etc. This might explain why no one
The title says it all. The pipwerks CaptivateController now includes a set method that enables developers to set a Captivate variable’s value using JavaScript. var myMovie = CaptivateController("Captivate"); myMovie.set("myCustomCaptivateVariable", "Hello!"); Give the new set method a spin! Read about the CaptivateController
While updating my CaptivateController script I noticed there have been some changes to the Captivate variables available to Captivate developers. I figured I should document them for future reference. Note that some variables available in CP3 and CP4 are no longer available. The following list should be exhaustive for CP5;
By popular demand, I’ve updated my CaptivateController to work with Adobe Captivate 5 (CP5). Since this is an open-source project, there’s no upgrade fee. (What? “Adobe” and “no upgrade fee” in the same paragraph?!) I kid, I kid… I’m a kidder. As you may have heard, Adobe