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.
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.
What a busy week. Flash is dead. Sort of, but not really. In case you haven’t heard, Adobe formally announced the discontinuation of Flash Player for mobile devices (“Flash to Focus on PC Browsing and Mobile Apps; Adobe to More Aggressively Contribute to HTML5“). Adobe employees struggled to come to grips with what has undoubtedly been a tough week for them — aside from the product news, they were also informed of massive layoffs (around Adobe 750 employees). Regardless of your feelings about Flash, your heart must go out to the families affected by a sudden job loss. Flash critics …
The pipwerks CaptivateController now includes a
My “Planets” example (How to Add Basic SCORM Code to a Flash Movie) has proven to be one of the most popular items on pipwerks.com. Unfortunately, it was designed as a quick example and had a bunch of flaws and shortcomings. It’s also about 3 years old and starting to show its age. Since people frequently contact me with questions — many of which were due to the flaws in the example — I decided to update the project.
The pipwerks SCORM Wrapper has been updated with a small patch for handling odd behavior in the Plateau LMS. Special thanks to Joe Venditti for the patch (and sorry for taking almost 2 years to add it to the codebase!). Get the latest version here.
About a week ago I tweeted:
from what i’m reading between the lines, #SCORM is dead to the ADL. they’re moving on. interesting timing considering #TAACCCT
I had no idea how much hand-wringing and consternation my off-handed comment would cause. It apparently caused (directly or indirectly) some heated discussions about SCORM being dead.
The problem is, I never said “SCORM is dead.” I said “SCORM is dead to the ADL.” Big difference.
An abstraction layer is a way of hiding complexities and maintaining cleanliness in your application. When integrating tracking support (SCORM, AICC, etc,) into an an e-learning course, it’s a good idea to abstract as much of the tracking code as possible. Here are some examples.