pipwerks

Geoff Stearns and Bobby van der Sluis have finalized SWFObject 2.0. It is no longer beta, and SWFObject 1.5 is now considered deprecated.

I decided to create a simple forum dedicated to e-learning development. I’m not saying I have the answers, but I’m hoping I can at least foster some good conversations and maybe get some of my peers talking and helping each other out. I’m also hoping to use the forum to promote web standards in e-learning development (as Martha says, “it’s a good thing”).

The WCAG Samurai Errata for Web Content Accessibility Guidelines (WCAG) 1.0 were published this week by the WCAG Samurai group.

There are a great set links for free development tools (validation services, browser toolbars and plugins) posted on the Web Access Centre Blog today:

Looking for alternatives to Bobby and WebXact? Try these!

By popular demand, the SCORM API Wrapper for JavaScript has a new feature: the ability to specify what version of the SCORM API should be used.

Also, I converted the AS2 demonstration FLA to Flash 8 format and posted it as a separate ZIP file.

The pipwerks SCORM wrapper examples have been successfully tested in SumTotal TotalLMS 7.6.
FYI, the examples’ imsmanifest.xml files required some modifications (the old manifests worked fine in the ADL test suites, but coughed a little when used in SumTotal TotalLMS 7.6). The JavaScript, ActionScript and HTML in the examples remain unchanged. If you’ve previously downloaded [...]

Here’s a simple example of how the SCORM AS3 class can be utilized. (This example uses SCORM 2004 calls.)

Finally got around to making some Flash files that demonstrate the pipwerks SCORM ActionScript classes. I’ve created examples for both AS2 and AS3. You can get them here.

Both of these examples have been successfully tested using the latest ADL test suites for SCORM 1.2 and 2004.

JavaScript SCORM_API_Wrapper.js now at v1.1.3. Includes important typo correction.

SCORM.as classes (AS2 & AS3) now at v1.01. Includes check for ExternalInterface availability and presence of required pipwerks JavaScript wrapper.

Understanding that we should be using standards and best practices throughout e-learning development, the question becomes “what standards and best practices should we follow?”

Here’s my attempt at outlining some basics.

I’m 100% positive I’ve missed a few things, and I’m pretty sure not everyone will agree with my statements. Why not join in and add your two cents?