Flash is almost gone and one thing I am having to do quite a bit of at the moment is remove swf files from my Lectora titles and replace them with something else that will work in future.
I used Flash files quite a lot with screen recordings of systems software. I would capture the steps in Captivate or a similar screen recording app and, rather than make it a simple video, I would include interactions so that the learner would have to locate and click on the right button to progress. In the past I would output these as swf files and insert them on the relevant page in the Lectora title.
With the ongoing demise of Flash I have to come up with a new solution. Here’s what I do. If anyone else is in the same position I hope that you find this helpful. First of all, in the screen recording software publish the recording as HTML5 and save the published files
Then, in Lectora:
And that’s it, really. If, like me, you’re finding yourself going through some of your legacy work to future-proof it, I hope that this is helpful.
Recently I sat in on the Lectora
Inspiration Wednesday, “The Magic Behind Powerful eLearning Design – Learning
Theory”. I always appreciate the efforts of organisations such as Trivantis to
reach out to the e-learning community and offer webinars such as this to
increase my knowledge as an instructional designer and developer.
The topic was really about
designing e-learning to ensure it met the learner’s needs but one of the other
things I took away from the session was the example; a board game style interaction
so I thought I would have a go at creating my own.
I wanted to make the game random so that it would give a more unpredictable element to the experience.
Clicking the die would generate a random number between one and six, and the counter would move the relevant number of spaces on the board. When it stopped a piece of information or a question would display. The learner would need to read the information or answer the question before they could move on to get to the end of the game.
Such interactions are appropriate
for presenting bite-sized information in a more engaging way than bullet
points. It does take longer to create, of course, so you would need to consider
whether the cost, time and effort is justified (although read on to learn about
a shortcut). Also the version I created included a random element – the throw
of the dice to move the counter – which meant that the learner might not see
all the content. As a result you might need to include a summary of the
learning points at the end.
It’s the sort of thing that could be used to help reinforce learning particularly on a topic where the learners feel they may already know the subject and may have got into bad habits. It’s an interactive way to present the information they should already know but may have forgotten as fun facts. The multiple choice questions scattered throughout add an extra element. If you would like to try the exercise, click on the screenshot below
There were a few things I needed to do to make this work.
First of all I needed to capture a random value to send the counter on its way around the board. Lectora is one of the better authoring tools when it comes to managing variables. Somehow to me, at least, it seems more intuitive than some of the other products available. It allows you to capture a random value to a variable when you are setting up an action. If you are interested there is a great video on the Trivantis website about working with random variable values.
The next thing that I needed to do
was to get the counter to move the relevant number of spaces. This was slightly
more problematic for a couple of reasons. First of all I needed to counter to
move from the square it had landed in which would obviously vary depending upon
the random value generated. Secondly I needed to get the counter round corners;
as you can see from the screenshot the board game meandered a little bit.
I spent some time wondering
whether I could capture the random value and use that to tell Lectora where the
counter had got to and needed to move from. In the event it seemed easier to
introduce a learner interaction to capture that information. The learner needed
to close the box that displayed when they reached the next square; I added an
action to that close button to tell Lectora where we were.
Lectora isn’t so great when it
comes to animating objects but it does have the move to action which allows you
to move objects from one position to another. It is possible to have objects move in a
straight line. In this module I wanted them to go around corners as well. The solution here was to have a series of move
to actions in action groups. The first action group would take the counter to
the corner and then trigger a second action group that would move the counter
on around the corner (in one or two cases there even needed to be a third
action group when the counter had to go around another corner). A crucial thing
was the timing of the actions. I needed to put a delay on the actions turning
the corner to make sure it didn’t happen until the counter had completed its
first move; otherwise it wouldn’t move all the way.
Another issue I needed to overcome was an appropriate naming convention for the action groups. I prefix them with the word “action” so that I can differentiate them from groups containing objects. The rest of the name is made up of a description of what the actions will do. In this case I also had to number the actions to keep track of them all. However, if the name becomes too long it is difficult to see it all in the dropdown list when you setting up action to run an action group, as you can see in the picture below. I had to come up with a shortened naming convention in this case.
I hope that you found this an interesting read on some of the practicalities on using Lectora in creating an interactive board game with random variable values and multiple move to actions. One of the joys of Lectora is that it has many ways of doing the same thing so I would be interested in others may have resolved the same challenge. Please add your comments in the comments field at the bottom of the page.
And that shortcut I mentioned? If you feel this interaction
might be useful for you but you don’t have time to create it yourself, for a
short time I am making the Lectora files for you to use to base your own
version on. Simply get in touch to find out more.
The latest versions of Lectora come with a range of animation effects, including fade and float in which makes for a smoother look and feel. However there doesn’t appear to be a rotate or spin animation effect. So this set the little wheels in my brain whirring and thanks to Math Notermann’s posting on the Trivantis Community I came up with a simple (ish) solution to make a spinning effect.
It is done completely with Lectora’s own capabilities
Choose your image
The first action is to create the object you want to spin. I chose a cog.
The next step is, in an image editing software; create multiple versions of your image at slightly different rotations. I rotated my image at 10 degree steps. Depending upon the complexity of your image you will not need to create images for every step. In my case the image rotated to 90 degrees looked the same as the original so, with 10 degree steps, I only had to create eight images.
Make sure you name all the images so they are easily identifiable.
Add your images to the Lectora title
And then delete all but the first one. This makes sure all the images are available when you apply the change contents action.
Alternatively, copy the images to the images subfolder for your Lectora title.
Set up timers and action groups
Add a number of timers to the page;
turn off the auto start and set them as initially hidden – you don’t need to be able to see them in run mode. Set them to count down and the timer to one second.
Create a number of action groups containing two actions:
Change contents of the image on your page to the next rotated image file
Play the next timer in line
Back in the timer set the done playing action to run each action group so timer one should run action group one, and so on.
Set an action to start the first timer – and the animation effect! Or you could set the first timer to start automatically.
How to get your rotation to stop and start in the same place
So you have set up a series of timers which, on finishing, sets off an action group to change the contents of the image to create the illusion of it rotating. Each action group then sets off the next timer to keep the spinning going. You might also have created a button that starts the first timer off.
What if you want to stop the spinning and start again from where you left off?
Hitting the start button again will jump back to the start image which does not allow for a very smooth rotation.
In each action group set an action to modify a variable that increments by one each time until you get to the last action group where you should reset it to its first value.
Now on your start button modify your action to play timer one only if the variable is at its first value. Then create a series of actions for all the other timers to start if the variable is at the relevant value. The stop button just needs to stop all of them.
You can now start and stop your cogs from whirring!
You can view the example and download the files from the Trivantis Community. If you have any comments, please add them below.
USING THE CHANGE CONTENTS ACTION TO HAVE BUTTONS CHANGE APPEARANCE
Lectora has an option to change the state of buttons but currently the states are active or inactive only (there is also a down and over state when you click or hover over them). There is no option to create a selected or visited state, for example. You may want to include these to allow the learner to see which buttons they have clicked to keep track of their actions.
Trivantis may have plans to update this but in the meantime a simple workaround is to create multiple image files for active, selected, visited and inactive, and use the change contents action to have them switch state.
I have created a couple of examples which you can view from the links below. You can also download Lectora library objects from the same links.
In the first example, the learners are required to click the buttons in order. There are three images for each button: inactive, active and selected. This example could be used if you need your learners to click on topics in a certain order. The inactive topics become active (and change to the active image) once the previous button has been clicked. A chosen button changes to the selected state until another button is clicked.
I wouldn’t normally do this but this was for a personal project so here are my workings out for a recent Lectora title I developed. It was all about checking your bicycle before heading out to make sure it is safe to ride.
The main thing I wanted to do here was apply the move to action I used in my earlier example to a specific project. I was also keen to explore the issue I discussed some time ago about second guessing your learners and provide them with the opportunity to complete the activity in any way they like. Hence the drawing.
Essentially what I wanted people to do was to move the image around to explore and click on the highlighted areas to
find out more about what to check for. I also wanted some way for the learner to be able to keep track of which section they were looking at so I included a thumbnail with a highlight that
moved with the learner’s interaction. I broke the image into quadrants but I wanted the learner to move to each quadrant in any order.
As before I had an action that modified the variables used to define the X and Y positions of the main image so the learners could move it around but in this case these were set to specific values (-650 and 35, and 35 and -367 respectively) rather than added to.
To move the highlight around the thumbnail I chose a different method. I had one variable with four potential values: TR (top right), TL (top left), BR (bottom right) and BL (bottom left). The highlight would jump to the relevant segment depending upon the value of that variable.
There were quite a few things to work out which is why I found it useful to lay our my ideas in a drawing.
I am happy to share the files with anyone who would like to see them in detail. Please add a comment below. And, of course, if you have a different way of doing this and are willing to share your ideas, please add those below as well.
I completed the Prudential Ride London 100 in 5 hours and 45 minutes. That’s the fastest 100 miles I have ever ridden. I was riding for the British Heart Foundation and there is still time to sponsor me. Just click on the button above.
When researching my recent blog posting on desktop vs mobile learning I was struck by something that should probably have occurred to me a long time ago.
Rapid authoring tools display content on a screen by screen basis
Most, if not all the rapid authoring tools create content based on individual screens: content is displayed on a single screen and the learner clicks next or performs a similar action to move on to the next screen. This could be seen as the legacy of PowerPoint (many of the products integrate with that application) but it goes back even further to that old fashioned technology, the book, where we turn the page to read the next bit.
The tyranny of click next!
This can lead to the tyranny of “click next”! Also, many websites no longer run on this basis. Typically the user scrolls or jumps down a single page to view the content. As I suggested in my earlier piece e-learning content should be developed to more closely match the learner’s experience of using the web generally.
This got me thinking whether you could do something similar with a rapid authoring tool such as Lectora and you can view the result here. I must admit it is one of the things I like about Lectora – it is a blank canvas ready for you to add your own ideas.
Lectora is a blank canvas upon which you can add your own ideas
I would be very interested in people’s comments, especially if they have attempted similar ideas. Also I would be happy to share the Lectora files if anyone else would like to adapt them for their own purposes. Just get in touch!
I completed the Prudential Ride London 100 in 5 hours and 45 minutes. That’s the fastest 100 miles I have ever ridden. I was riding for the British Heart Foundation and there is still time to sponsor me. Just click on the button above.
I am currently working on a project researching the use of MOOCs (Massive Open Online Courses) so I thought it would be useful to try one for myself to find out what they can be like for a learner. I chose an open course from one of the major providers on a subject of personal interest to me (photography). Here are a few of my early thoughts.
Before I go any further it is probably best to define a MOOC. It can be a very vague term but the key features of a MOOC appear to be:
It is online
It can incorporate short videos and activities
Learners can access help via an online forum
It can include peer mentoring and assessment
I think the crucial aspect of a MOOC is the opportunity it offers dispersed learners to work together to meet their learning needs. This is the Massive part. It is the end-user interaction that is important as it gives the learner to opportunity to learn from the content but also from their peers.
End-user interaction is a crucial characteristic of a MOOC
The earliest MOOCs were developed in conjunction with large academic institutions and were open to all. More recently there has been a move towards creating MOOCs for corporations and other closed institutions. The course I took was one of the former run in conjunction with MOMA, the Museum of Modern Art. It was for personal use (the subject was the art of photography) so unlike a professional course there may be different issues surrounding motivation and completion (typically only 4% of participants complete a public MOOC). Having said that the organisers of the event had many efforts to keep the participants engaged both before the programme and throughout.
These included a welcome email which apart from offering practical information on accessing the course, also helped build anticipation so encouraging the learner to buy into the course and retain their motivation. The welcome email included useful information on how to stay the course such as inviting a friend to complete it with you, and sharing your progress on social media. Secondly, the course itself was relatively short (six weeks) and really only required about an hour’s commitment each week. Having said that, there was additional reading the learner to uncover more about the subject. Finally there was a good mix of materials to keep the learner engaged such as videos, podcasts and a live webchat.
The programme consisted of three parts: the actual content which included text, videos and slide shows; a discussion forum; and assessments.
The content could be viewed on different devices and the videos could be downloaded to my iPad. However different technology was needed to make some of the content work – there was a mobile and desktop friendly versions of the slideshows (and the former didn’t always work).
The first week of the discussion forum was an opportunity for the participants to introduce themselves. It was a bit intimidating on day one to view the empty discussion forum (there was no input from the moderator at this point) and wonder what I should say. Eventually someone else beat me to it. In later weeks the discussion was more directed with a specific question being asked. I noted that there appeared to be less interaction between the participants at this stage. The questions could encourage lengthy responses and it was possible that others found it difficult to reply in an appropriate manner.
The third part of the programme was the assessment. Whilst participation in the weekly discussions was optional the learner could not proceed without completing each week’s assessment. The programme included a process to identify the learner completing the assessment, in this case using my webcam and keyboard strokes. The questions themselves were very often little more than a memory test so I quite quickly got into the habit of going straight to the assessment, printing the screen and having it by my side as I worked through the rest of the content.
So the key things I got out of the programme (apart from new perspectives on looking at photographs) was that:
There needs to be a process of building anticipation beforehand to encourage motivation.
Some means of accountability needs to be encouraged to maximise completion. In this case it was about doing the course with a friend. In an educational or work environmental this could equate to fellow students or work colleagues.
The content needs to work across different platforms successfully.
The purpose of discussion forums needs to be considered carefully. In week one they were a chat facility – in later weeks they were more a means of submitting short essays.
If multiple choice questions are used the wording of the questions needs to be thought about to avoid them simply being a memory test
Lectora 16 is the latest version of Trivantis’ rapid authoring tool.
They’ve jumped straight from 12 to 16, using the current year (possibly to avoid unlucky 13). The selling point of the new version is responsive design – being able to create content that can be deployed to different sized platforms from desktop down to phones.
Before Lectora 16 if I needed to create content for different sized platform I had to create different Lectora files
Previously with Lectora I either created multiple versions of the same module, maybe with the theme templates to quickly repurpose the content; or I put some code that detected the platform and resized accordingly. This didn’t allow you to layout the content differently for the different sized platform – which is where Lectora 16 comes in. It allows you to visualise how it will look on different platforms so that you resize and reposition objects accordingly.
So how does it work in practice?
I thought I would find out so I rebuilt an existing piece of content in Lectora 16. You can view the results here.
If you have had any experience with Lectora 11 or 12 the overall appearance doesn’t look too different. There are two main differences, however.
The first is on the splash screen which now includes the option to create a new responsive title; there is still the option to create standard e-learning content. If you change your mind and decide that you need to create a responsive module after all you can’t switch; you’ll have to start from a new title. Of course, you can always import the frames from the old module into the new one.
The second is the new toolbar with a series of different devices from a desktop in the middle to tablets and phones (landscape and portrait). The two things to recognise at this stage are (a) the arrows extending out from the desktop – the layout of the other devices depend upon this one; and (b) the colours of the different devices – which we will return to shortly.
When developing responsive content start from the middle – the desktop version. Layout the objects on the screen; the text boxes, images, etc, and add all the interactivity as required. Once you have that sorted move out to the next stage; the tablet. Begin with the landscape version as they may not be too many changes to make here; check the content, and re-position and resize accordingly.
As you do so, take a look at the sizing handles and note how they change colour to match the colour of the device at the top of the screen. This lets you know that it will be different to the desktop version. Changes made here will cascade down to the phone level. You can of course make changes specific to that level as well.
At the lower stages you can substitute different sized imagery. This is particularly useful when switching between portrait and landscape views. Also you could use it display different information; have an exercise in landscape and get the learner to turn their device to see more information once they have completed the exercise.
I found it great way to develop content for multiple platforms.
It’s cleverly laid out so the developer can quickly see what they’re doing for each size of content. The colour coding works well in this regard. It doesn’t need any coding knowledge, just some patience switching back and forth to get everything laid out just so. But it is less work than having to build multiple versions of the same file. Publishing is no different except that the published folder contains three new subfolders for each device. File size does not look overly massive.
I did experience one or two issues. The first one was that text in the text boxes did not always appear as I expected. Sometimes it would be cut off by the edge of the box. The best practice appears to be to over-size the text boxes to allow the text room to grow. This fits in well with the best practice of not overloading content on smaller devices.
The second issue was more to do with the appropriateness of re-purposing the same content for different sizes, especially a mobile phone. Whilst you can deliver complex exercises on a desktop or tablet, a mobile phone may be more suitable to smaller bite sized activities. So you may need to consider whether the content you are creating is suitable for delivery on every platform. However you can have unique content for each device – simply drag it off the page when it’s not needed. And I have not tested this yet but I imagine there are ways that you can create specific pages that are only accessible in certain formats. I would be interested to know if anyone has had a go of this yet?
You can view my effort here. Note this module was created in a trial version of Lectora 16 so you will see a small window display to start with.
If you use rapid authoring tools and need to create simple content for multiple platforms, Lectora 16 could be for you.