01. July 2014 · Comments Off on Articulate Storyline – a few things I want to remember · Categories: Articulate Storyline
This is another brain dump post – but as I thought it could be useful to Articulate Storyline users, I’m going to make it public.

A few things I want to remember:

  1. If you want to allow people to skip sides and are using formative assessment with feedback and aren’t fussed about the grade – but still want to track completion in a Moodle, create a results slide then delete all the display options (grade, review quiz, etc). Ensure the formative assessments allow infinite retries so the user can’t move on until they’ve gotten the question correct. The result will be a 100% grade and THAT will indicate completion.
  2. The error windows that pop up automatically (as in when someone tries to skip answering a question in a quiz) come from the player and you can format them there.
  3. Set Browser size in the OTHER menu of Custom on the player. Display at user’s current browser size and Scale player to fill browser window means no more white space if exporting to an LMS as a SCORM package.
13. December 2012 · Comments Off on Sweet 16 or so things I need to remember about Articulate Storyline · Categories: Articulate Storyline, Technologies

Another messy blog post that’s all about things I want/need to remember…

1) It caches like STEEL TRAP. If you make changes, you need to click Preview to see them. Just changing, saving and hitting play will not always show your new edits.
2) To bring in bullet points one by one, you need to choose an animation type in the animation tab – then select – by first level paragraph.
3) Video embedded in the slides will not provide the option to expand to full screen. If you have small details, you will need to upload your video and may be able to embed the player – YouTube works a treat. I was unable to do so using our proprietary media server Viostream as its player requires javascript be embedded in the header tags of page templates. Just trying to trigger Javascript didn’t work.
4) CTL Z doesn’t work as expected. I found I bounced back to previous slides. Not sure why this happens, but don’t assume it will work as expected.
5) Don’t assume the sound quality you hear as you edit or preview is the final version. It is a compressed preview version – you need to publish to hear the full quality.
6) Javascript doesn’t work in Preview mode. Test slides with Javascript by copying them into their own project and publishing.
7) Set text boxes to “Do Not Autofit” – this sometimes doesn’t seem to stick between computers.
8) If using a line in mic for screen captures, go to screen capture mode, Turn off mic (line in won’t come up as an option anyway, I disabled my mic in Windows 7 just to be sure), select your line in as SPEAKER.
9) When timing several objects on screen to audio, where possible, record audio in chunks and match up to events.
10) Watch for events that aren’t timed to last until end of screen if you want them there. Some are set to appear for a set length of time and won’t allow you to adjust slide duration. Others cut out just before the end and disappear.
11) When shortening the length of a slide, if an event has a fixed time it will blow past its cue point so that it can stay on for its set length of time.
12) Set up a name for the variable you want to change that you’ll remember – the more generic, the more margin for error. Ensure you’re changing a T/F value or text as relevant.
13) Trigger order matters! Where possible, find a template that does what you want and backward engineer it. There are loads out there programmed by clever people.
14) To pull out MP4 vidoes when using Storyline for screen captures, you should set up a New Project first, just for your screen capture. Once a screen capture is complete, you’ll insert it into a slide – pick the single slide option – then need to go back up to screen capture, act like you want to insert it again, but this time right click on the video you see and save it as MP4.
15) If you plan on publishing Storyline as a SCORM package in an LMS, you will need to program the Next key on your last slide to Exit.
16) If you plan on publishing Storyline as a SCORM package in an LMS,the end message “The content has ended. You may close this window” isn’t useful for Moodle courses. To change it, publish it but DON’T EXIT THE PROJECT and DON’T ZIP. Go to the folder where the output was published, open the named folder, go to te LMS folder, right click on the Goodbye.html file and open in your fav editor (I use Notepad ++). Edit the message to something like “To return to the main course page, click on the course name in the horizontal text navigation at the top left of this page.” Save the file and close it. Go back to the Articulate project and THEN zip the project using the options in the publishing window there. Then, upload the zip to Moodle. You could of course get fancy and program a button or link to link directly back to the course page…

26. July 2012 · Comments Off on Customising Articulate Storyline’s LMS Goodbye message · Categories: Articulate Storyline, Moodle 2.2
I’m on a steep learning curve with a new piece of software (Articulate Storyline) and writing tutorials about another piece of software that I’m not offay with. Not a comfortable place to be but the challenge is pushing me and being uncomfortable is okay now and again. It’s when I end up learning the most.

I’ve learned that Moodle doesn’t handle SCORM comfortably – no matter what the SCORM package, whether it opens in the same window or a new one, horizontal and vertical scroll bars show up – even when the learning object is set to size dynamically. It’s as if Moodle builds in a 10 pixel or so pad in reverse – always 10 pixels width and height are hidden somehow. This doesn’t matter so much on height, but it’s a pain in the bum on width!

With Articulate Storyline, another issue is that regardless of whether or not you’ve set the player to open in a new window, it outputs the same message to an LMS along the lines of: You’ve finished the content. Close the window. 

Unfortunately following this instruction exactly would result in students closing their Moodle sessions unintentionally.

I found the file to edit, but I learned that I needed to do it after Publishing from Articulate but before allowing Articulate to zip up the package. I tried zipping the package myself and got an error message from Moodle when I tried to use it.

Here is what I do to create a custom goodbye message for an Articulate Storyline package:
  • Publish the file
  • Go to folder
  • Go to the LMS folder
  • Right click on the Goodbye.html file
  • Open it in Notepad ++
  • Edit and save the file
  • Go back to Articulate
  • Zip the file using the link in the publishing window
  • Upload to Moodle
Got a better way to do this? Please let me know. And if you know how I could create a link in the Goodbye.html document back to the course, I’d greatly appreciate it. Using _blank, _parent, _top just loads the course page into the iFrame.