Today I decided to whip up an AppleScript that automates the generation of the <file> nodes to make my life a little easier. If you're on a Mac, you may find it useful, too.
Category: e-learning
AppleScript for generating SCORM manifest
Clean out the root of your SCORM 2004 package
With just a little effort, you can declutter the root of your SCORM package by sticking the schema files in a subfolder.
Flash support is increasingly a minefield
Back in 2011, I mentioned that Microsoft was about to halt development of the Silverlight plugin, that Flash mobile was being discontinued, and that Adobe recommended HTML5 for enterprise RIA development instead of Flex, which was being open-sourced. My post was a little long-winded, but the short version was: whoa, the times-are-a-changin’, it’s getting dangerous to rely on browser plugins.
Over the last year, the situation has evolved in an interesting way — browser support for plugins (especially Flash Player) has been considerably restricted by browser vendors due to repeated security vulnerabilities in Flash Player and Java.
Automatically disabling Flash Player
In May 2012, Apple’s Safari browser began automatically disabling outdated versions of Flash Player: “Out-of-date versions of Adobe Flash Player do not include the latest security updates and will be disabled to help keep your Mac secure.” If a webpage contains a SWF but the installed edition of Flash Player is deemed out of date, Safari will display a “blocked plugin” message and inform the user they need to download the latest edition of Flash Player at adobe.com. This change came with Adobe’s blessing.
In January 2013, Mozilla introduced a global “click to play” mechanism that disables ALL plugins in Firefox by default, except the latest edition of Flash Player: “Our plan is to enable Click to Play for all versions of all plugins except the current version of Flash.”
To Adobe’s credit, Flash Player updates are being released at a fast clip to address known security vulnerabilities. Unfortunately, this has a nasty side effect: you’re very likely to have an outdated edition of Flash Player when you try to view Flash content on a website. (By my unofficial count, there have been at least 13 updates over the past calendar year, averaging about once a month.)
At a recent job, I managed a small network of Macs in classrooms. The Macs were set up to use Adobe’s ‘automatic updates’ feature for Flash Player, but they never seemed to update fast enough — we received numerous complaints from classroom users who couldn’t view Flash content because Safari blocked it.
Internet Explorer’s on-again, off-again relationship with Flash Player
I previously mentioned that Microsoft’s Windows 8 ‘Metro’ mode disabled all plugins, including Flash Player; Microsoft said Internet Explorer in Windows 8 Metro mode “provides an add-on–free experience, so browser plugins don’t load and dependent content isn’t displayed“.
In May 2012 Microsoft changed their minds and enabled Flash in Metro mode. BUT… Microsoft will ship Flash Player as a component of IE 10 (much like Google Chrome does), and will restrict which sites are allowed to run Flash! “While any site can play Flash content in IE10 on the Windows desktop, only sites that are on the Compatibility View (CV) list can play Flash content within Metro style IE.”
In other words, if you don’t have Microsoft’s blessing, your Flash site will not work when viewed in Metro mode.
Update: @chris_sage pointed me to a post by Microsoft written just three days ago where they apparently changed their minds again — almost a year after saying they’d require a whitelist, they now say they support Flash Player by default in Metro mode without requiring sites to be whitelisted.
What it boils down to…
If you develop Flash-based content, it will be more and more of a challenge to provide a smooth, problem-free user experience. For e-learning developers, one of the original lures of Flash was the ubiquity of Flash Player; Flash made it easy to provide the same e-learning experience across browsers and platforms. Due to fragmentation in Flash support, this no longer appears possible.
- Adobe says: No Flash Player for mobile devices.
- Microsoft says:
No Flash Player on Surface tablets (or other Windows 8/RT tablets) unless the user switches to desktop mode OR gets on our whitelist for Metro mode.We love us some Flash! But we’ll manage the security updates ourselves, thank-you. - Mozilla says: Only the latest edition of Flash Player for Firefox.
- Apple says: No Flash Player on Apple iOS devices, and only the latest edition of Flash Player for desktop Safari.
- Opera says: Flash Player on desktop editions of Opera? No problem. Flash Player in Opera Mobile? Don’t get mad at us, Adobe stopped providing Flash Player for mobile devices!
- Google says: We control Flash Player for Chrome (desktop) ourselves. No worries. Flash Player in Chrome on mobile devices? Don’t get mad at us, Adobe stopped providing Flash Player for mobile devices!
The browser vendors are enforcing their will. You don’t have to be a Flash-hater to see that building Flash-dependent sites is a minefield.
For those of you in e-learning who depend almost completely on Flash-based courseware, it’s a good idea to start looking for alternatives.
Important Adobe Captivate SCORM template update
Introducing SWFRightClick
Adobe Captivate currently ships with a 3rd-party JavaScript utility named RightClick.js, which enables the Captivate SWF to detect when a user right-clicks the SWF. While upgrading the Captivate publishing templates, I realized RightClick.js wasn’t built to work with SWFObject 2.x and suffered from a few shortcomings. I modified the Captivate template’s SWFObject code to get around the issue, but marked it down as something to revisit when I have the time.
Now, I’m happy to report I’ve created a replacement for the RightClick.js utility, creatively named SWFRightClick. It uses the same approach to handling right-clicks, but does it with a completely new codebase and a few extra goodies. SWFRightClick is compatible with every edition of SWFObject, and is free to use (MIT license).
Check it out on GitHub. I plan to fold it in to my Captivate publishing templates very soon.
New SCORM 1.2 Template for Adobe Captivate
By popular demand, the SCORM 1.2 edition of my revised SCORM publishing templates for Adobe Captivate 5.x is now available on GitHub.
Further Tweaks to the Adobe Captivate SCORM Publishing Template
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.
Cleaning up Adobe Captivate’s SCORM Publishing Template, Part 7: Giving the Revisions a Home
I decided to post the revised Adobe Captivate publishing template to GitHub, where it can be easily copied, forked, and updated. I moved a few bits of markup/code around, added some configuration options (such as the ability to turn off centering, turn on logging, and require SCORM when loading), and added a ton of comments to explain some of the new options. Hopefully it's all self-explanatory.
The State of Adobe Captivate’s SCORM Support
I've heard rumors that the upcoming Captivate 6 will contain a completely revamped SCORM system that eliminates many of the issues I've covered. If this is the case, many of us will surely be elated, perhaps enough to pay for yet another upgrade. This could also help explain why Adobe hasn't addressed the current SCORM publishing template; a complete overhaul of the existing SCORM system -- including the ActionScript code inside the published SWFs -- is a considerable amount of work.
Cleaning up Adobe Captivate’s SCORM Publishing Template, Part 6: Bugs & Scope Creep
For this blog post, I was going to write a summary of the changes to the template and wrap up the series. Instead, I'm looking at ways to increase the template's flexibility and hot-rod it for some cool other stuff.