Aaron definitely is the man if you guys
want to integrate Flash and SCORM—I’d be glad to contribute in some
form as well.
One other thing Aaron, is there anything
in the works from ADL or CTC to take advantage of the Flash 8 virtual machine’s
intrinsic ability to synchronously communicate with _javascript_? Maybe the
External Interface API should be brought up on the ADL forum so that the LMS
vendors—who sometimes live under rocks—are aware of the capabilities.
It would be killer to see an elegant and mature marriage between Flash, LMS and
SCORM tool offerings.
Regards,
Brooks
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Silvers
Sent: Thursday, August 18, 2005
1:17 PM
To: [email protected]
Subject: Re: [osflash] Open Source
Interaction Components
_javascript_ was chosen because of its vendor neutral ubiquity. The SCORM spec
absolutely requires that all communication with the LMS be done via a
_javascript_ bridge. Vendors are more than welcome to write their LMS in any
language they choose as long as the exposed adapter can be found by pure
_javascript_ and communicates with SCO's via _javascript_.
As I've mentioned in an earlier post, the SCORM spec is final and you will
not see changes forthcoming ever (other than bug fixes).
The AICC spec which was a forerunner of SCORM (SCORM in fact uses a subset
of the AICC cmi data model) allows you to communicate with an LMS via http
using almost any server-side language you want. _javascript_ was chosen to
replace this in order to establish a reusable and interoperable standard.
I agree its not elegant and in general is a pain in the ass, but just
thought I'd try and give you a bit of insight.
Regards,
Brooks Andrus
Spot on, correct, Brooks. SCORM is designed ot solve the following
problems:
- §
Accessibility –
Content can be identified and located when/as it is needed.
- § Adaptability –
Content can be tailored to individual and organizational needs.
- § Durability –
Content doesn't require modification as software systems change/upgrade.
- §
Interoperability –
Content functions in multiple applications, environments and
software/hardware configurations regardless of the authoring
tools/platforms used.
- § Reusability –
Content is independent of learning context, thus can be used in different
contexts for different learners
Since I've been using Flash since, oh... FutureSplash, and I've been
contributing to the spec, as well as authoring content examples demonstrating
(and explaining) communicaiton with SCORM 2004, Phil Double asked me to chime
in and see if I could help you out.
I'm currently working on a template for Flash MX 2004/Flash 8 that uses the
Flash/_javascript_ Integration Kit to talk directly to either a SCORM 1.2 or
SCORM 2004 API (it will autodetect in _javascript_). From there, I would
think your components would be easy to construct.
I'm planning on presenting on this at MAX 2005 (do a search for "Robust
E-Learning" under the presentations). If you guys are serious about
wanting to do something, I'd like to help.
--
-a-
Aaron E. Silvers
[EMAIL PROTECTED]
http://www.mrchompers.net
------------------------------------------
"when the five senses and the mind are still, and reason itself rests
in silence, then begins the Path supreme." - neodämmerung
