SCORM RTI Wrapper automatically inserts the HTML attributes and JavaScript code required for compliance with the ADL SCORM v1.1. If the target page already has an onLoad or onUnload event handler the pre-existing handler is automatically called after the new handlers. This effectively "wraps" your existing HTML page and makes it a SCO.
Version 1.1.1 of the SCORM RTI Wrapper improves compatibility with Netscape
browsers, and uses more robust code to find the SCORM API in the parent or opener
windows. To update pages that used earlier version, open the page with Dreamweaver
and run the command again. Be sure to set the status and advanced options for
the desired effects, as the command will not "remember" the previous
settings when it replaces the old code. Likewise, any customizations made within
the automatically inserted handlers or other code will be lost, unless you record
and re-enter your changes. The new version defaults to associating the call
to the API.LMSFinish method with a button action as its trigger.
Advanced developers may edit the source to the SCORM RTI Wrapper command itself,
and change the default button placement and title as indicated in source code
comments.
For more information on the ADL and SCORM see: http://www.ADLnet.org
The SCORM specification requires compliant content to:
| Optional calls to set status | |
| Set status onLoad: | |
| Trigger for LMSFinish: | 'Finish Lesson' button |
| 'onUnload' event | |
| Set status based on trigger: | |
|
|
|
| Advanced options | |
| Disable LMSInitialize | |
| Disable LMSFinish | |
| Disable 'No API found' alert | |
Using the optional status features will insert the proper API.LMSSetValue() function call into the corresponding event handler(s). The 'Finish Lesson' button setting is the preferred trigger for LMSFinish because using the onUnload handler may have unpredictable results when closing the window or unloading the parent frameset provided by a LMS. The button text and position may be customized after running the extension. To change the default button position and text, advanced developers may edit the source code to the SCORM_RTI.htm extension file found in the Dreamweaver Commands folder.
Advanced users may also choose to disable LMSInitialize and/or LMSFinish if they want to create multiple-page lessons. For example, the first page would call LMSInitialize but disable LMSFinish, and link to a subsequent page. Subsequent pages would disable LMSInitialize and LMSFinish, until a final page that disables only LMSInitialize (and perhaps sets the status to complete).
Finally, the developer may choose to disable the default JavaScript alert that states, "Warning: API object not found in window or opener." To disable this warning simply check the box next to the label Disable 'No API found' alert. Regardless of the setting of this checkbox either 'API found' or 'API not found' will appear in the browser status line, as appropriate.
To make your preferred selections for the optional status settings and advanced options become the new defaults, use the Defaults... button in the main dialog of the SCORM RTI Wrapper extension.
Check for the latest version
of SCORM RTI Wrapper extension at:
http://exchange.macromedia.com or http://www.macromedia.com/learning