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.

cmi.core.exit & cmi.exit

Ok, I just had to write a quick blurb about this one: in about 3.5 years of using SCORM in my own course code, I had never used cmi.core.exit (SCORM 1.2) or cmi.exit (SCORM 2004). Seems incredibly daft of me now that I’ve taken a few minutes to review the documentation.

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.

Things to consider when working on a training project

I read not one, but three great blog posts today regarding what kinds of questions you should asking yourself when working on a project. Two of the blogs were not specific to the e-learning industry, but they apply nonetheless.

HTML 5: The strong element

In the new HTML 5 proposal, the strong element is being modified to represent “importance rather than strong emphasis.”