Most e-learning developers don’t care about SCORM and only (begrudingly) learn enough to get the job done. I don’t blame them. This brings up the never-ending question when it comes to using SCORM in courseware: What are you really trying to do with SCORM?
Good post from Michael Feldstein at e-Literate:
There’s something fundamentally contradictory about open standards being developed behind closed doors.
…
Over the past 18 months, I have had the privilege of participating in the IMS work on a regular basis. During that time, I have mostly kept my mouth shut about the openness issue. Out of respect for [...]
The talented Cameron Moll has posted a link to a Web Accessibility Checklist prepared by Aaron Cannon, a (blind) member of his web development team.
Aaron’s checklist is an easy-to-understand list of accessibility dos and don’ts. Most of these are so simple and easy to implement that there’s really no excuse to NOT use them [...]
Ran across this short but useful blog entry from Layers Magazine.
I know many people who use assorted ’screencasting’ tools (Captivate, Camtasia, Firefly, etc.), and my guess is that very few of these people give much thought to the hardware they use for their projects. Hardware has a huge impact, and can be the difference [...]
I’ve had a number of people ask me why I haven’t extended my SCORM helpers (the JavaScript-based SCORM API wrapper and the two ActionScript classes) to completely remove the need to know any of the “cmi” calls. I have three reasons: SCORM is not that simple, the functionality between SCORM versions is significantly different, and extending the helpers that far means writing a complete (non-standardized) replacement syntax for SCORM.
A recent post in the elearning development forum reminded me that I forgot to post some unpublished Captivate variables I dug up a while back.
Sorry to give everyone the runaround, but after trying Google Code for a month, I found it seriously lacking and not very fun to use. Therefore as of tonight, all of my SCORM files (and other goodies) are back at pipwerks.com on a dedicated downloads page.
The SCORM API wrapper (v1.1.7) has been updated to automatically set the initial course status and the exit status.
The point of my SCORM API wrapper is to make working with SCORM easier. These two new functions are intended to ensure you follow best practices with your SCORM code while reducing the amount of tedious code you will need to write for your course.
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.
Today, I’m going to explain how to add SCORM code to a plain HTML file. This example uses SCORM 1.2 syntax, but as I explain at the end of the tutorial, it’s really easy to edit the code to use SCORM 2004 syntax.