PDFObject 2.3 released, new site
PDFObject 2.3.0 has been released and is available immediately on NPM and related CDNs. The new pdfobject.com features more thorough documentation and examples.
Latest news regarding pipwerks’ projects, including the SCORM wrapper and PDFObject.
PDFObject 2.3.0 has been released and is available immediately on NPM and related CDNs. The new pdfobject.com features more thorough documentation and examples.
After 15 years, I have decided to retire the E-Learning Technology and Development Google Group. It supported 1070 members and 783 discussions from 2009-2024.
Made a minor update: scorm.quit() was setting a value (cmi.exit) but not invoking scorm.save() (aka Commit()) prior to termination.
View the latest update on GitHub
By popular demand, the SCORM 1.2 edition of my revised SCORM publishing templates for Adobe Captivate 5.x is now available on GitHub.
Since the code for my templates will remain on GitHub, I highly suggest checking in from time to time to see if the code has been updated. I won’t be posting a blog entry on pipwerks.com for every little edit I make to the code.
The pipwerks CaptivateController now includes a set
method that enables developers to set a Captivate variable’s value using JavaScript.
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.
The pipwerks SCORM Wrapper has been updated with a small patch for handling odd behavior in the Plateau LMS. Special thanks to Joe Venditti for the patch (and sorry for taking almost 2 years to add it to the codebase!). Get the latest version here. Comments Bobby wrote on August 10, 2011 at 7:31 am: Thanks for the update Philip! I test my content outside of a LMS environment. In that case, the code you've introduce causes a javascript error since win.top.opener is null. To combat this, I check for win.top.opener before checking for win.top.opener.document. I'm not sure this is worth adding, as I realize I'm in a unique situation. Just thought I would share my findings. Thanks again! philip wrote on August 10, 2011…
Three years have passed since PDFObject 1.0 was released, and the browser landscape has changed dramatically. I figured it’s time to dust off PDFObject and see if it can be improved and/or updated for today’s browsers.
In 2008 I posted a quick writeup on how I dealt with cross-domain security issues for some of my e-learning courseware. Since then, I’ve had a lot of people contact me with various questions and for example files. Tonight I decided to revisit the topic and whip up some quick example files.