Cleaning up Adobe Captivate’s SCORM Publishing Template, Part 2: HTML
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.
Cleaning up Adobe Captivate’s SCORM Publishing Template, Part 1: Introduction
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.
HTML5, Flash, Silverlight, and your courseware
Bye bye Flash, Flex, and Silverlight
CaptivateController Updated to Support Setting Variable Values
The pipwerks CaptivateController now includes a set method that enables developers to set a Captivate variable’s value using JavaScript.
Lion Server compared to Snow Leopard Server
Comparing my recent experience with Lion Server to my experience with Snow Leopard Server.
SCORM “Planets” Example Updated
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.
SCORM Wrapper updated for improved Plateau support
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. Comments Bobby wrote on August 10, 2011 at 7:31 am: Thanks for the update Philip! I test my content outside of a LMS environment. In that case, the code you've introduce causes a javascript error since win.top.opener is null. To combat this, I check for win.top.opener before checking for win.top.opener.document. I'm not sure this is worth adding, as I realize I'm in a unique situation. Just thought I would share my findings. Thanks again! philip wrote on August 10, 2011…
Using the object element to dynamically embed Flash SWFs in Internet Explorer
This is a journey into the madness of Internet Explorer. Yes, there is a happy ending.
Sniffing Internet Explorer via JavaScript
I’ve been reviewing bug submissions for the SWFObject project and was reminded of a big problem with SWFObject 2.2: the JavaScript technique it uses for detecting Internet Explorer does not work in Internet Explorer 9.