I'm getting close on the SCORM builds so that they work in blackboard for assignments as well as the other LMS's. One thing I've noticed though is that creating a scorm package of a single html page creates a zip file at over 14MB. If I set this to be a portable build, that drops to about 130KB.
Since these archives need to be uploaded to the LMS and might be emailed around to other instructors, it would be nice to not bundle all the JS in the archive. A few options:
- Educate instructors to set portable="yes" in publication whenever they build a scorm file.
- Automatically set portable="yes" for scorm builds.
- Add a new publisher switch that prefers remote/hosted javascript and css, and make it's default with scorm be to use the hosted version
- Don't add a new publisher variable, but internally always use remote/hosted javascript for scorm.
1 and 2 are really not ideal, since the portable build also messes up interactives and annotated prefigures (and maybe some other things). 4 would be easiest, but while I'm touching the code, it would be relatively easy to add the new publisher variable.
Thoughts?