Skip to end of metadata
Go to start of metadata

Generative Learning Object Maker version 2

At the European LAMS 2009 Conference, Tom Boyle from the Learning Technology Research Institute at the London Metropolitan University, presented the Generative Learning Object Maker (version 2). I was very impressed on how easy it was to create learning objects with GLO. So I decided to give it a go and see if I could put together a learning object that then I could import into LAMS Share Resources activity.

The Generative Learning Object Maker v2 is an authoring tool that supports lecturers in developing, analysing and sharing learning designs. It's an Adobe Air application available for download here.

Using GLO to create Learning Objects

GLO Pre-release version!

Note that in this demo we have used a GLO pre-release version. The final release will be available in August 21, 2009 from the GLO Maker website

I created a very simple LO using one of their templates and within a three minutes I had created a LO with pictures an assessment and reflection. Clearly, I didn't properly design the object (smile), just trying to create a simple multimedia learning object to use. Once I had created it, then I publish the object into my local file system.

In the directory where I put the object I could see an GloWebPlayer.html file that is the file that "plays" the LO. Given that most webservers will pick up index.html or index.htm, I changed the name file to index.html instead. Locally, the LO runs perfectly. The swf player picks up the details from the .glo file (xml) and plays the content/views accordingly. Neatly self-sufficient and self-contained LOs.

Importing GLO Learning Objects in LAMS

Now, I zipped up the whole directory and put uploaded into a Share Resources activity in LAMS author as a shared zipped website. LAMS will then place the files it finds on the zip file in its content repository and whenever they are called from the browser, it will deliver them accordingly.

The first time I tried to preview it within LAMS, the pictures didn't show up. I saw that some of the files requested still had the absolute path to files. So for instance if I had uploaded the file from a directory called "/tmp/mypictures", then the reference to this absolute path was making failing to get the images because, of course, the LAMS webserver didn't have that path. So I realized that the .glo xml file had the hardcoded absolute paths, so I simply removed them and just left the references to the images as relative to the LO root directory.

Zipped it back up again and re-uploaded it back in Shared Resources... now it worked without a glitch! (smile)


I have shared the sequence in the LAMS Community, so you can see this in action by yourself:


Uploading GLO Objects as shared zip websites

Playing GLO Objects in LAMS learner

  • No labels