Hi ET
Sorry this is abit long winded but I think I've covered everything on one go.
Very basically the CD's are 'stand alones' and the SCORM functions are handled by a Javascript API which functions pretty much like part of a Learning or Content Management System. However there are some fundamental differences they only work on a single session basis, that is everything done is forgotten so next time you open the module you're back at the beginning.
If you use a SCORM or AICC compliant CMS or LMS then the API handles passing info from the module to the L/CMS. These work differently so you can have multiple sessions on the same module (if you allow it) and return to the point you finished at on your previous session. Also information such as scores, responses etc can be passed via the API to the L/CMS.
See for info and links on SCORM and AICC
http://www.aicc.org/
http://www.adlnet.gov/
Condensing the above.... It's not a function of a stand alone to offer the full capabilities found in an L/CMS, only to provide a basic environment that the module can function in.
Re-load (a design editor)can let you manipulate a completed SCORM module or join components into a module, you can also access most of the API's variables. It is fairly straight forwards but does pre-suppose a bit of knowledge of the SCORM API.
They also have a stand alone SCORM player (try making a module, exporting it in SCORM or AICC format and then try and run it). It will complain because it can't find the API to handle the transactions, that function is built into the L/CMS. You can run them using Reloads player but remember it is a stand alone allowing the SCORM API to be used on modules built for an L/CMS but cannot replace the functionality of that L/CMS.
http://www.reload.ac.uk/scormplayer.html
Or at Source forge
http://sourceforge.net/cvs/?group_id=76357
You could 'make' your own recorder much as you have done using actions and some javascript. This is more part of the functionality you get in the L/CMS and in a stand alone would be very clunky and probably not massively more sophisticated than you already have implemented. Probably the only real improvement would be to bundle all the information into one final information dump.
It might be worth you having a look at Jonathan Yassens strand "Saving data using flash example here" it's a part of the answer but you'd need to be able to use Flash action script to take it any further.
Luckily there are only really seven different requests the SCO (shared content object, 'the module') makes using the Javascript API, as far as I remember in SCORM 1.3 these are Initialize(), Terminate(), getValue(), setValue()and three others that are used as diagnostics. 2004 extends the use of these a bit.
If you play with flash on this avoid using FSCommand() to talk to the API as it is platform specific to windows. Search Adobe for Flash SCORM, again most of these will give you a run time environment (stand alone player again) or a full set of interactions with the SCORM/AICC API. There isn't much that bridges the two areas.
The very short answers is with a stand alone you get play back with limited functionality. To get full functionality you use a C/LMS.
Hi ET
Sorry this is abit long winded but I think I've covered everything on one go.
Very basically the CD's are 'stand alones' and the SCORM functions are handled by a Javascript API which functions pretty much like part of a Learning or Content Management System. However there are some fundamental differences they only work on a single session basis, that is everything done is forgotten so next time you open the module you're back at the beginning.
If you use a SCORM or AICC compliant CMS or LMS then the API handles passing info from the module to the L/CMS. These work differently so you can have multiple sessions on the same module (if you allow it) and return to the point you finished at on your previous session. Also information such as scores, responses etc can be passed via the API to the L/CMS.
See for info and links on SCORM and AICC
http://www.aicc.org/
http://www.adlnet.gov/
Condensing the above.... It's not a function of a stand alone to offer the full capabilities found in an L/CMS, only to provide a basic environment that the module can function in.
Re-load (a design editor)can let you manipulate a completed SCORM module or join components into a module, you can also access most of the API's variables. It is fairly straight forwards but does pre-suppose a bit of knowledge of the SCORM API.
They also have a stand alone SCORM player (try making a module, exporting it in SCORM or AICC format and then try and run it). It will complain because it can't find the API to handle the transactions, that function is built into the L/CMS. You can run them using Reloads player but remember it is a stand alone allowing the SCORM API to be used on modules built for an L/CMS but cannot replace the functionality of that L/CMS.
http://www.reload.ac.uk/scormplayer.html
Or at Source forge
http://sourceforge.net/cvs/?group_id=76357
You could 'make' your own recorder much as you have done using actions and some javascript. This is more part of the functionality you get in the L/CMS and in a stand alone would be very clunky and probably not massively more sophisticated than you already have implemented. Probably the only real improvement would be to bundle all the information into one final information dump.
It might be worth you having a look at Jonathan Yassens strand "Saving data using flash example here" it's a part of the answer but you'd need to be able to use Flash action script to take it any further.
Luckily there are only really seven different requests the SCO (shared content object, 'the module') makes using the Javascript API, as far as I remember in SCORM 1.3 these are Initialize(), Terminate(), getValue(), setValue()and three others that are used as diagnostics. 2004 extends the use of these a bit.
If you play with flash on this avoid using FSCommand() to talk to the API as it is platform specific to windows. Search Adobe for Flash SCORM, again most of these will give you a run time environment (stand alone player again) or a full set of interactions with the SCORM/AICC API. There isn't much that bridges the two areas.
The very short answers is with a stand alone you get play back with limited functionality. To get full functionality you use a C/LMS.