<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Julian<br>
re 1.<br>
I was thinking about navigation to pages (using Navtopage script from a
hyperlink)or an external Rlo htm. So to make the wizard more user
friendly perhaps there should be <br>
separate nav to page property and nav to url of external RLO
property. if you are using the menu to go to pages then the behavior
requested is desirable and if you select nav to page for the first link
then the behavior is the default. Understand thats a bit complex but I
think having pages in the menu is desirable even if there are not very
many. They may just be provided the glue to link the RLOs together or
the external RLO may be a mode detailed presentation of information etc.<br>
<br>
<br>
2. Thats great<br>
<br>
<br>
3. Really just ease of user naviagtion. If you do not have many
sections, but a lot of links in say one sections and just few links in
the other sections. ie need the space then keeping the section choices
as close together is desirable rather than having a lot of white space
when a sections without many links is active simply because you need it
for one section.<br>
<br>
<br>
On 28/04/2010 6:55 AM, Julian Tenney wrote:
<blockquote
cite="mid:826FA59EEA0A914FA34AECF56FD831A804185259@VUIEXCHA.ad.nottingham.ac.uk"
type="cite">
<title></title>
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta content="MSHTML 6.00.6000.17023" name="GENERATOR">
<div id="idOWAReplyText99954" dir="ltr">
<div dir="ltr"><font color="#000000" face="Arial" size="2">1. You
mean open the first learning object? Automatically?</font></div>
<div dir="ltr"><font color="#000000" face="Arial" size="2">2. Yes, no
problem. Good idea.</font></div>
<div dir="ltr"><font face="Arial" size="2">3. Not sure what you
mean..? I see the space, not sure what you want to put in it.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="Arial" size="2">Fow now, I stayed away
from having pages in the menu, which you had in your original idea, but
they can be done - I imagine they are like a nested page - text and an
optional image? I'd like to get the menu functionality nailed first.</font></div>
</div>
<div dir="ltr"><br>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a> on behalf of Peter Snowball<br>
<b>Sent:</b> Tue 27/04/2010 21:54<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> Re: FW: [Xerte] structuring LO's needing a topic
hierarchy<br>
</font><br>
</div>
<div>Looks good<br>
<br>
A few simple nice to haves depending on how easy to do<br>
<ol>
<li>Fire the hyperlink for the first link when you open a section
ie push on the section button ?<br>
</li>
<li>A background colour around the link to show the user which link
is active - may be via css ? </li>
<li>Adjust the height of the accordion for each section - so you
can make the section buttons below the visible text of the open
section, with a default (height) white panel behind.<br>
</li>
</ol>
<br>
Attached mock up in paint<br>
<br>
Thanks<br>
<br>
Peter<br>
<br>
<br>
<br>
On 28/04/2010 1:58 AM, Julian Tenney wrote:
<blockquote cite="" type="cite">
<style>
<!--
font-face
{font-family:SimSun;}
font-face
{font-family:SimSun;}
font-face
{font-family:Calibri;}
font-face
{font-family:Tahoma;}
font-face
{font-family:Consolas;}
font-face
{font-family:"\@SimSun";}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{
color:purple;
text-decoration:underline;}
pre
{
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{
font-family:Consolas;
color:black;}
span.EmailStyle19
{
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{
font-size:10.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);">Whaddya reckon? See
attached.</span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);"></span> </p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);">It’s simple but
works well enough – could add in more options, etc,</span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);"></span> </p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);">J</span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; color: rgb(31, 73, 125);"></span> </p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
<p class="MsoNormal" style="margin-left: 36pt;"><b><span
style="font-size: 10pt; color: windowtext;" lang="EN-US">From:</span></b><span
style="font-size: 10pt; color: windowtext;" lang="EN-US"> <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a>
[<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="mailto:xerte-bounces@lists.nottingham.ac.uk">mailto:xerte-bounces@lists.nottingham.ac.uk</a>]
<b>On Behalf Of </b>Peter Snowball<br>
<b>Sent:</b> 27 April 2010 13:28<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> Re: FW: [Xerte] structuring LO's needing a topic
hierarchy</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left: 36pt;"> </p>
<p class="MsoNormal" style="margin-left: 36pt;">A menu wizard or
wizards for page / external RLO navigation would be a tremendous asset
to Xerte. <br>
<br>
In a recently completed project we created a "menu" rlo that linked to
pages within the menu RlO and also hyperlinks to the index htm of
another three rlos. (see attached screen shot) It was a copy (using
buttons) of the Ispring / Articulate std power point to flash
interface. <br>
<br>
We have been advised to have menus visible at all times so users can
navigate with one click to where they want to go and back to where they
have come from. Ispring cannot do this but Xerte can. Also Ispring
cannot create a frame and have genuine nested learning sequence. The
problem with the the current TOC is that it is not visible, is a pop
up, three clicks and only shows the top level . See attached screen
shot of Ispring navigator - always visible, content is one click away,
highlights where you are in the rlo, uses scroll bars and pretends to
show nested content but in fact shows slides (pages) sequentllty. <br>
<br>
One option worth considering perhaps is to have options on how the TOC
operates and displays eg : always visible (left or right) - and shows
levels as expandable tree.<br>
Say looping through the XML to find the nested pages.<br>
<br>
myPageXML = Icon.XMLElement.getChildByName(myPageName); ???<br>
<br>
As an alternative one could populate some thing like an accordion
navigator with all levels displayed and a forward and back button -
without disturbing the basic linear navigation of the player. While
buttons worked fine on our menu we were on the verge of running out of
stage space for buttons on rlos and will need something like an
accordion navigator for the current RLOs we are developing.<br>
<br>
Peter Snowball<br>
Department of Economic Development<br>
Tasmania<br>
<br>
On 27/04/2010 6:41 PM, Julian Tenney wrote: </p>
<pre style="margin-left: 36pt;">Could do it as a page type in the main template, 'Menu' that would take options either as urls or as page names.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">Options could be presented using a variety of controls: radio buttons; combo box, buttons, maybe hotspots...</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">I'm not sure how to handle the interface considerations. I must say I do like the idea of keeping the router separate from the content. However you do it, there will always be someone who wants to route at a different level. Ultimately, everything is linear, it's granularity that is the consideration. If you want all the routing options, then you might have to make very granular content, but that way the content stays separate from the navigation.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">-----Original Message-----</pre>
<pre style="margin-left: 36pt;">From: <a moz-do-not-send="true"
href="mailto:johnathan.kemp@ntlworld.com">johnathan.kemp@ntlworld.com</a> [<a
moz-do-not-send="true" href="mailto:johnathan.kemp@ntlworld.com">mailto:johnathan.kemp@ntlworld.com</a>] </pre>
<pre style="margin-left: 36pt;">Sent: 26 April 2010 20:27</pre>
<pre style="margin-left: 36pt;">To: Xerte discussion list</pre>
<pre style="margin-left: 36pt;">Cc: Julian Tenney</pre>
<pre style="margin-left: 36pt;">Subject: RE: [Xerte] structuring LO's needing a topic hierarchy</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">A router template sounds like a good idea. It could be really useful to be able to create a number of separate learning objects and to then be able to combine them into a variety of different courses. A course being defined by the router template(s) and the learning objects they called. This would facilitate the re-use of learning objects.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">However I can also imagine situations in which branching is desirable within a learning object. Which is why I created the Routed Tabbed Navigation page wizard, and am also working on a few more routed page wizards. </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">If the router template could also receive as an alternative to a learning object url the name of a page in the current learning object, then it could do double duty, both as a hub for learning objects and as a router within a learning object. If it was flexible, as you suggest it could be, in the ways it presented the options, then it could save me the trouble of creating a variety of Routed Page Wizards :-) (I am assuming that it would be possible to convert it once the template was available to a page wizard).</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">I appreciate that routing within a learning object presents some navigation issues. Linear sections require Next and Previous buttons, whilst these buttons are not always appropriate where routing is being used. Rather a Home button and a Back button based on a LIFO queue may then be preferable. For example I used the Routed Tab Navigator to set up a simple tree structured expert system type learning object, in which every page was based on the Routed Tab Navigator. Previous and Next are then irrelevant but Home and Back become critical.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">The problems arise when you combine sequences and routed sections within one learning object. Maybe the solution is to include the sequenced sections as framework pages with next and previous navigation added on the frameworks Entry Frame and have Home and Back buttons as part of the main navigation.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">Creating the template as a separate template would limit it to being a hub for other learning objects. Including it in the Page Templates project wide template would give it the potential to be used within a project.</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">So any chance of including the capability to route to pages as well as learning objects? If so what might the chances be of offering optional Home and Back buttons on the Xerte Navigation?</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">Kind regards</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">Johnathan</pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">---- Julian Tenney <a
moz-do-not-send="true" href="mailto:Julian.Tenney@nottingham.ac.uk"><Julian.Tenney@nottingham.ac.uk></a> wrote: </pre>
<pre style="margin-left: 36pt;"> </pre>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;">
<pre style="margin-left: 36pt;">_______________________________________________</pre>
<pre style="margin-left: 36pt;">Xerte mailing list</pre>
<pre style="margin-left: 36pt;"><a moz-do-not-send="true"
href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a></pre>
<pre style="margin-left: 36pt;"><a moz-do-not-send="true"
href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a></pre>
<pre style="margin-left: 36pt;"> </pre>
</blockquote>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;"> </pre>
<pre style="margin-left: 36pt;">_______________________________________________</pre>
<pre style="margin-left: 36pt;">Xerte mailing list</pre>
<pre style="margin-left: 36pt;"><a moz-do-not-send="true"
href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a></pre>
<pre style="margin-left: 36pt;"><a moz-do-not-send="true"
href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a></pre>
<pre style="margin-left: 36pt;"> </pre>
<p class="MsoNormal" style="margin-left: 36pt;"><br>
<br>
<br>
</p>
<pre style="margin-left: 36pt;">-- </pre>
<pre style="margin-left: 36pt;">Peter Snowball</pre>
<pre style="margin-left: 36pt;">Dept Of Economic Development</pre>
<pre style="margin-left: 36pt;">Tasmania</pre>
</div>
<br>
<p>This message has been checked for viruses but the contents of an
attachment may still contain software viruses which could damage your
computer system: you are advised to perform your own checks. Email
communications with the University of Nottingham may be monitored as
permitted by UK legislation. </p>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Peter Snowball
Dept Of Economic Development
Tasmania</pre>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Xerte mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Peter Snowball
Dept Of Economic Development
Tasmania</pre>
</body>
</html>