A common thread in many of the posts I’ve been reading is that standards do not lead to innovation, but rather that innovation leads to standardization.
Thoughts and an addendum for my SCORM 2.0 white paper submission
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?
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.
Here’s a quick tutorial for adding basic SCORM functionality to an existing Flash file. This tutorial aims to demonstrate just how easy it can be to add SCORM functionality to an existing Flash movie.
Please note that this tutorial uses ActionScript 3 and SCORM 1.2, but the same principles apply for ActionScript 2 and SCORM 2004.
I’m currently working on a tutorial explaining how to add SCORM code to an ordinary Flash file. Here’s a teaser: a very simple Flash movie I made using some images from NASA. It’s called PLANETS!