While I laud the effort to standardize eLearning
transactions using SCORM, I just can't sign on to a system that is (in
my view) so fundamentaly flawed. Perhaps I am misunderstanding, so
correct me if I am wrong, but SCORM requires a page-turning interface with
content, with a round-trip each time a "learning object" is loaded and used. It
also requires very specific scoring syntax, correct? I did some research into it
a year ago, and was mortified by the adherence to _javascript_. Beyond
that shortsighted spec, I found the API confining from an architecture
standpoint.
During my research, all of the work done using Flash
was based on the paging model of traditional web pages. Flash was pretty
much simple eye candy (Did someone say FutureSplash?) in every example I
found. On top of that, the user interactions were the classic, boring
checkboxes, radio buttons, etc. SCORM doesn't appear to be designed for an
asynchronous, non-"traditional" interface that is the strength of
Flash.
If anyone can post links to sites that give a neutral
overview of SCORM and the pros/cons, please do. I am sure my complaints
aren't new to anyone in the SCORM world, but if there is something I am missing
I am all ears.
Tim
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
