Tag: javascript
A SCORM-ready template: Part 1A. Features
 Here’s a screenshot of the template, showing part of the left-hand navigation expanded. Note the previous/next navigation buttons at upper right, which are automatically created based on your list of pages, as is the progress bar and page numbering at upper right. |
Randomizing Captivate Quizzes
Captivate quizzes are easy to create, but they lack some often-requested features. Even using version 2, it is difficult, if not impossible, to randomize questions within Captivate. The following method will alter the html wrapper generated when you publish a Captivate project so that it chooses from a bank of alternate Captivate SWF files when the page opens.
Download example HTML wrapper file
When you publish to Flash (SWF) in Captivate, Captivate creates an HTML wrapper which contains the SWF file in an object tag. (Usually titled “ProjectTitle.htm”) There is a variable, “strURLFile ,” which determines which Captivate file is launched. In the unaltered file, this variable is set to the project title you set when you published.
Continue readingGoLive’s Javascript IDE
Although I don’t use Adobe GoLive much for day-to-day work, it has certain features that are hard to find anywhere else. One of them is a rather impressive Javascript authoring environment. It gives contextual hints,
Continue readingCaptivate and SumTotal 6.5: Part 1. Setup
Part 1. Setup | Jump to Part 2: Enable SCORM output>>
I’m involved in producing some Captivate-based assessments for use with SumTotal 6.5. There are many settings and variables that must be set correctly to get everything working to our specifications, so it took some serious testing to figure out the best settings.
Hopefully this will shorten the time for anyone with similar needs.
Continue readingThe requirements: We are producing competency-based learning modules and assessments. Users must complete the multi-SCO assessment with a score of 100%. They aren’t that easy, so it is expected that they will need several if not many tries to complete one SCO. Each interaction within any given SCO will allow three tries before the slide moves on.
Each SCO will allow an infinite number of tries.
Debugging and troubleshooting HTML and javascript
Firefox, the web developer’s debugging tool of choice
The best browser to use to check javascript errors is Firefox, hands down. Other browsers have some error reporting, but none give you anywhere near the detailed information as Firebug, an addon to Firefox. The extensions available allow you to snoop into every aspect of your page, and into the communication between page and server.
You will need to get several Firefox extensions:
Firebug
Firebug is the one extension I can’t live without. It shows errors in javascript, css, allows you to inspect the HTML source, computed style, events, etc.
Docent, SCORM and cross-browser issues
During our recent Docent LMS implementation, one of the most difficult tasks I was faced with was to ensure SCORM activities work if browsers other than IE were used.
The specific cross-platform issues fell into several categories:
Definitions of terms used in this article:
Passing a variable in the URL to turn on and off layers in another page
I have a series of five flowcharts in a tabbed layout, one flowchart per tab (seem to be doing tabs a lot lately). I wanted the user to be able to click a link on another page, and have the flowchart page open to the correct flowchart layer. A working example is here:
Switch layers on the next page by clicking a link
When I tried setting the value of a variable on the new page, it worked in some browsers but not others, probably because some computers are slower at loading pages than others, and the necessary layers would not be loaded in time for the variable to have something to populate.
Continue reading