Internet Explorer Quietly Fades Away
A personal retrospective on Internet Explorer, the browser we loved to hate.
LearnSWFObject.com domain being retired
Pour a cold one for SWFObject and learnswfobject.com.
On Converting Flash to HTML
The limitations of browsers and the HTML5 spec mean you can’t expect a fully 1:1 conversion from Flash to HTML, regardless of libraries like CreateJS.
Flash support is increasingly a minefield
Just say no to Flash.
The State of Adobe Captivate’s SCORM Support
I’ve heard rumors that the upcoming Captivate 6 will contain a completely revamped SCORM system that eliminates many of the issues I’ve covered. If this is the case, many of us will surely be elated, perhaps enough to pay for yet another upgrade. This could also help explain why Adobe hasn’t addressed the current SCORM publishing template; a complete overhaul of the existing SCORM system — including the ActionScript code inside the published SWFs — is a considerable amount of work.
HTML5, Flash, Silverlight, and your courseware
Bye bye Flash, Flex, and Silverlight
Lion Server compared to Snow Leopard Server
Comparing my recent experience with Lion Server to my experience with Snow Leopard Server.
Is SCORM Dead?
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.
Instructional Technologist, Explained
I bill myself as an instructional technologist, which means I’m often met with blank or puzzled stares. I thought it might be useful to explain my rational for using this title.
SOAP for SCORM
LETSI’s Run-Time Web Service (RTWS), a proposed modification of SCORM to use SOAP for communication rather than the current JavaScript model. I presented the first half of the session, covering the basic “what” and “why” ideas while Ben covered the technical details (“how”) in the second half.