pipwerks

Standards don't foster innovation, they codify it

After all my ruminating on SCORM 2.0 the last couple of weeks, it was interesting to read about the latest news regarding the ECMAScript standard. It was even more interesting to read some of the reactions, including those from Adobe’s Dave McAllister (link no longer available) and Yahoo’

SCORM 2.0 white paper submission

I submitted my white paper for SCORM 2.0 today. I don’t see it listed on the LETSI site yet, but I’m hoping they received it and that it will be added soon. I wanted to share a few things about my experience writing that paper. First of

Choosing a specific technology for your e-learning courseware

This question came in via email. I figured I would post it (keeping the author anonymous) because these are very common questions, and maybe this post can help other people out. I also want to give others the opportunity to throw in their 2 cents! The question(s): I am

What do you want *your* SCORM to do?

Most e-learning developers don’t care about SCORM and only (begrudingly) learn enough to get the job done. I don’t blame them. The other day I was reading some old Drupal community posts (circa 2005) about adding SCORM functionality to Drupal. One comment stood out: SCORM was the big

Extending the SCORM wrapper and ActionScript classes

I’ve had a number of people ask me about extending my SCORM helpers (the JavaScript-based SCORM API wrapper and the two ActionScript classes) in order to completely remove the need to know any of the “cmi” calls. For instance, being able to do something like this: scorm.bookmark = "

pipwerks © 2026