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.
What happens if the browser window containing your course is closed by the learner before the course finishes sending data to the LMS? If you're not careful about how you've coded your course, you can lose some of the data.
A number of people have recently asked me about the
scorm.save() function in the pipwerks SCORM wrappers. What is it, and when should it be used?
For instance, I’m trying to write an easier way to work with the cmi.interactions model, and also trying to add more error-checking that will look for gotchas such as exceeding the length limit of suspend_data.
I’m looking for good ideas. How do you handle your cmi.interactions? What kind of code shortcuts would you like to see? How can working with SCORM be made easier? I’d love to hear your ideas, just post them as comments below or send them to me on twitter.
This project — just like my previous wrappers — will be freeware, either MIT license or GNU license, so no worries about me running off and selling your ideas!
(FYI: for now I’m focusing on SCORM 2004 — SCORM 1.2 should be retired — but depending on how things work out I might add backwards-compatibility for SCORM 1.2.)
I recently emailed a shortlist of good SCORM development resources to a colleague, and figured I should probably post a list here, too. This is a quickie list, and I'm sure I'm leaving someone out. If you know of any resources I've missed, please add a link in the comments. This list is presented in no particular order.
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.