In this multi-part series, I will walk through the files Captivate outputs when publishing to SCORM 2004, pointing out the bad parts and suggesting alternatives when needed. At the end of the series, I will provide a fully-functional SCORM 2004 publishing template you can use with Captivate 5.5.
The pipwerks CaptivateController now includes a set method that enables developers to set a Captivate variable’s value using JavaScript.
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.
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.
If you spend any time using Captivate to create SCORM-conformant courses, you’re bound to have run into an issue or two that caused you to read some Captivate forum posts. Almost without fail, someone will mention that the solution to their problem was changing the value of the magical g_intAPIType JavaScript variable from 1 to 0 or from 0 to 1.
So what the heck is g_intAPIType, and why does changing it make a difference?
Someone recently asked me if it was possible to customize Captivate’s SCORM template to reduce the need for manual editing after publishing. In her case, the manifest needed to be edited to include SumTotal TotalLMS’s custom SCORM extensions. The answer is yes. Here’s how.
The CaptivateController has been updated to fix the gotoSlideAndPlay and gotoSlideAndStop bugs.
It took me much much longer than I anticipated, but I am happy to announce the new CaptivateController utility.
This controller is not a simple rehash of the original pipwerks.captivate.control utility; it is a complete re-write that adds a number of extra features.
The folks at Adobe recently published a list of Captivate 4 variables. While it’s a solid list, it’s not really a complete list.
As alluded to in a previous post, I’ve whipped up a simple JavaScript utility to help you control your Captivate SWFs using JavaScript.
The biggest selling point for this utility is that it not only contains all of the built-in Captivate ‘variable’ functionality, but it also contains some extra functionality created by chaining some variables together.
