SCORM: Why not write the API Instance in ActionScript

Question

We're working on a SCORM compliant system for a major blue
chip. We have a mixture of old AS1 and AS2 content, along with
shiny new AS3 modules, all of which needs to be intergrated into a
single system. As I have posted about elsewhere here, there seem to
be some issues with fscommand() and ExternalInterface when content
from mixed virtual machines is loaded into Flash Player - the
connection to Javascript just fails silently (even after a
successful call to ExternalInterface.available ).
We've been looking, therefore, at simply building an API
instance in AS3.0, and using robust http calls to communicate from
there to the LMS. The SCORM specification calls for the API
Instance to be written using ECMAScript. Every implementation we
can find seems to equate this with Javascript but my understanding
(and please correct me if I'm wrong, anyone), is that Actionscript
is itself an ECMAScript dialect. That being so, it ought, we think,
to be possible to create the API instance within Flash.
Does anyone with direct experience of this know if an
application using an Actionscript API would be SCORM compliant or
if there is any other way we can avoid using the Flash > JS API
> LMS channel which has been giving us such problems?
Many thanks in advance for any responses.
Jude Fisher
JcFx Limited
http://www.jcfx.eu

Answer 1

I found why: The handler function should take an EffectEvent parameter.