[Xerte] Making conditional itineraries with Xerte

[ron at kccsoft.com]

If I can jump in here I have a question about paging.

 

Is there a place (which I may have not discovered yet) where I can see the
internal variables Xerte is tracking? For instance the 'CurrentPageNum' var
in AW. I'd like my paging to track the 'CurrentPageNum' in Xerte and when
'CurrentPageNum' = 'PageCount@"XerteFrameworkIcon"' to go back to the menu
page. Any example of how to do that?

 

Also - I understand Xerte uses Actionscript 1 (which is great, I have no
desire to learn the latest versions) - any suggestion on the best reference
to AS1 for a relative beginner?

 

Thanks

RonM

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Tenney Julian
Sent: Tuesday, June 17, 2008 3:48 AM
To: Xerte discussion list
Subject: RE: [Xerte] Making conditional itineraries with Xerte

 

Hi,

 

There isn't currently a template for doing such an interaction, so you'd
have to build one. How complex that is really depends on how complex you
want to make the scenario. If it's as simple as presenting a stimulus and
have the user select from a list of options, and then present feedback in
the form of text with perhaps optional images, it would be quite easy.

 

It would also be easy to sequence a number of these pages together, thus
creating a linear sequence of essentially multiple choice questions.

 

Take a look at the pageTemplate.xtp in the [xerte]/wizards folder. It has a
number of page types, one of which is multiple choice question. You could
adapt that, or perhaps it works just fine. To create a project from this
file, double click the xtp file. Xerte will make the new project and open it
(sometimes it doesn't open - just double click the rltfile in the folder you
created the project in if this happens).

 

Is the scenario you want to support as simple as that? If it gets more
complex (i.e. if a and b but not c then go to page x, else if a not b or c
then goto page y else if not a or b and c then goto page z) then you hit two
problems: the code is more complex, and the template editor gets more
complex too. I'd highly recommend keeping it simple.

 

HTH,

 

J

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20080617/e6b1a585/attachment.html