I bill myself as an instructional technologist, which means I’m often met with blank or puzzled stares. I thought it might be useful to explain my rational for using this title.
And so ends another whirlwind of a week known as DevLearn.
Could the timing have been any better? My San Francisco Giants (yes, my Giants!) won the World Series and decided to have the largest parade in San Francisco history on the first day of DevLearn. It just happened to be a block from the conference site, which was A-OK with me! In their honor, I wore my Giants jersey the entire day.
While updating my CaptivateController script I noticed there have been some changes to the Captivate variables available to Captivate developers. I figured I should document them for future reference.
By popular demand, I’ve updated my CaptivateController to work with Adobe Captivate 5 (CP5). Since this is an open-source project, there’s no upgrade fee. (What? “Adobe” and “no upgrade fee” in the same paragraph?!) I kid, I kid… I’m a kidder.
If you spend any time using Captivate to create SCORM-conformant courses, you’re bound to have run into an issue or two that caused you to read some Captivate forum posts. Almost without fail, someone will mention that the solution to their problem was changing the value of the magical
So what the heck is
g_intAPIType, and why does changing it make a difference?
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?
The IMS wants your personal information before they’ll let you read their public standards.
If the new standards are written as poorly as this press release, it’s going to be 1,000 pages of useless spec.