Adobe eLearning Suite and Captivate 4 released

Adobe has officially announced Captivate 4 and the Adobe eLearning Suite. My first thought upon finding out about the eLearning Suite a few months ago: “Why should I buy the eLearning Suite if since I already have CS3/CS4? The only real difference seems to be the inclusion of Captivate, which I can get separately, and Presenter, which I probably won’t even use.” The answer is…

Storing Adobe Captivate interaction data in a database: Adobe wants your feedback

Adobe is investigating the needs of Captivate users regarding how you would like to store your quiz interaction and score data. As you may know, Captivate already provides a mechanism for sending this data to an LMS via SCORM or AICC (and a couple of other options), but the Captivate team also knows that some of you are asking for more.

They want to hear from YOU about your situation and what you would like to be able to do with the Captivate score and interaction data. For example, would you store data directly to a database without using an LMS, or perhaps use web-based services to store the data?

This is your chance to tell them exactly what you’d like to see. Please write up a short summary of the functionality you’d like to see, and a clear example of how you would use it, if it were available. Be sure to use a valid email address when posting so Adobe can contact you for clarification if needed.

Introducing the pipwerks Captivate Controller JavaScript utility

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.

Control a Captivate SWF using JavaScript: The basics

JavaScript can control the playback of Captivate-generated SWFs. I posted some examples about a year ago (example one, example two), but someone recently reminded me I haven’t posted any instructions or explanations for my examples. Here’s a quickie explanation of how you can control a Captivate-generated SWF using JavaScript.

Unpublished Captivate variables

A recent post in the e-learning development forum reminded me that I forgot to post some unpublished Captivate variables I dug up a while back.

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

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.