Step 3 – The First Test

Now that I’ve got the frameset and a skeletal API in place, I think I’ll try running a SCORM course and see:

  1. Does it find the SCORM API that I’ve set up?
  2. If it finds it, what errors occur?

This will provide some good guidance on where to go next.

A quick search of the Internet doesn’t reveal a lot of sample courses out there. However, in the article on Output Options in Captivate, Andrew Chemey does provide a zip file that contains a SCORM 1.2 sample. For the time being, I’ll use that sample to test my rudimentary SCORM interface.

On a test web server, I set up the files like this:

My Test Configuration

Note that I’ve had to add an index.html file to the course folder since the sample course start file is called ‘Simulation.htm’. My index.html is simply a redirect and looks like this:

<title>Starting ...</title>
<meta http-equiv="refresh" content="0; URL=Simulation.htm">
<body bgcolor="#ffffff">
<p>Starting ...

Now I take the plunge and run it by pointing my browser to:

  http://[my test server]/rte01/rte.html

OK – here’s the good news – it finds the API frame and calls the JavaScript API functions starting with LMSInitialize. It also fires off a host of JavaScript alerts as it tries (and fails) to write and read ‘persistent data’ to the LMS that isn’t there. Press the OK button often enough and the course does run through to the end.

This is what happens!

So, what do I know now? I know that the frameset and the JavaScript API are OK in principle, but I now need to start looking at how to read and write data to the “LMS” database. And this is where things start getting a little more complicated.

Be Sociable, Share!
This entry was posted in Run Time Environment. Bookmark the permalink.

One Response to Step 3 – The First Test

  1. Pingback: Desarrollando un LMS(con soporte de SCORM)

Leave a Reply

Your email address will not be published. Required fields are marked *