-
Notifications
You must be signed in to change notification settings - Fork 34
Quick Start
Mark Statkus edited this page Jan 1, 2016
·
6 revisions
All the configuration, all the APIs, and all the docs = fatigue.
- Totally get it.
Bypassing the full documentation this is as lean as it gets.
- Take QUnit-Tests/js/scorm.bot.pack.js and add it to your project (SCO).
- At the bottom of your HTML, you need the following (minimal) -
var scorm = new SCOBotBase({
debug : true, // true or false
exit_type : 'suspend', // suspend, finish
success_status: 'unknown', // passed, failed, unknown
}),
SB = new SCOBot({
happyEnding : true
});
- SCOBot will fire a 'load' event letting you know it is safe for you to load your presentation.
SCOBotUtil.addEvent(SB, 'load', function(e) { // in 4.x.x
// SCOBot already took care of connection to the LMS and Initialize!
// Do everything else you would do to fire up or resume your content here.
player = new SCOPlayer(); // or player.init(); You customize this!
return false;
});
- Package your content using SCORM 1.2 or SCORM 2004
- Deploy on a LMS
- Assign, and test.
Please take note of frameworks, and other web technologies which tend to load up on their own before you've established a connection to SCORM. This can dictate if you should wait for SCOBot to connect to the Runtime API on the LMS. Note the 'load' event above.
Any issues, concerns or feedback - make contact