<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There is an <info> tag which will put information at the bottom of the screen for a page type.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><info><![CDATA[Here is info on this page]]></info><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It’s bit restricted though, space wise, but could include a link to the real help in html format in the common folder, or online, maybe on the wiki.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><info><![CDATA[For info, click <a href=”yourhelppage.htm”>here</a>]]></info><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-left:36.0pt'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> xerte-bounces@lists.nottingham.ac.uk [mailto:xerte-bounces@lists.nottingham.ac.uk] <b>On Behalf Of </b>Kemp Johnathan<br><b>Sent:</b> 27 April 2011 14:30<br><b>To:</b> Xerte discussion list<br><b>Subject:</b> [Xerte] Xerte 2 : Help File for Wizard Forms in PageTemplates, On-line Toolkits and Page Wizards<o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'><br>I recall a new page being added to PageTemplates a while back that allowed you to define non-rectangular hot-spots. At the time I found the Page's form a bit confusing. Because unlike other pages that had an option in the form to add a hot-spot to an image, this page worked differently. Hot-spots were added using Xerte's drawing capabilities. Some form of help file that I could have accessed whilst completing the page's wizard form could have explained this to me, showing me how to complete the wizard. This would have been really useful.<br><br>The issue of helpfiles became even more significant to me the other day. <br><br>I have been looking recently into how PageTemplates (and presumably therefore On-line Toolkits) and the Page Wizards can share a common set of .rlm files.<br><br>I think I have found a way of avoiding the need in Page Wizard .rlm files to have the "learningObject[0]" addition to data calls that currently forces the Page Wizard's .rlm files to be so different from the PageTemplates .rlm files. This should result in it being relatively simple to develop a new Page Wizard and to then port it across to PageTemplates or On-line Toolkits, thus making the Page Wizards a valuable platform for the community to use to develop new pages.<br><br>To demonstrate this I have been working on converting the Inventory Page Wizard for inclusion in a PageTemplates issue (At present the Inventory Page is unique to Page Wizards). It was this that raised the issue (opportunity) once again of having a help file.<br><br>The Inventory Page lets you define a series of group titles e.g. Auditory, Visual, Kinesthetic. It then allows you to define a series of questions in which each answer option can be allocated to one of the groups. Thus as users answer the questions they build up scores in each of the groups. On completion of the Inventory the user is presented with a graph or pie chart that displays their scores for each group, either as an absolute number or as a percentage. E.g. It might in the above example show the user as 20% Visual, 30% Auditory and 50% Kinesthetic.<br><br>To achieve the above the wizard form that supports the page has a number of options that take a little explaining. This is achieved in the Page Wizard by having a "read me" script block that does nothing in terms of how the page functions but just contains commented text that tells the page designer how to use the form. This can work in a Page Wizard as users of Page Wizards can access the underlying structure of the page. But as a solution it is a bit crude and not particularly user friendly. More critical is that this method cannot work in a PageTemplates / On-line Toolkit environment, because access to the underlying page structure is not available.<br><br>Page Templates and On-line Toolkits have a nice feature that is not available to Page Wizards and that is the display of a thumb-print image of the page, to help the user select the right page. This is achieved by having an image file for each page present in a "thumbs" folder. The appropriate file is referenced in the xwd file for each page.<br><br>I believe it would be useful and helpful to users if we could have another folder perhaps called "help" which contained a simple help file that described how to use each page template's wizard form? The vision I have is that on opening the page's wizard form that the form would provide a link to the help file and that on clicking the link the help file would open in a separate window so that you could refer to it whilst completing the form. If the wizard form was closed then the help window would close as well.<br><br>What would be even better is if this system could also work for the Page Wizard version so that the same help was available to Page Wizard users. There is already support in Page Wizards for the inclusion of files in a common folder that are then copied to the project's common folder if they are not already present. The Page Wizards could deliver their help file in a similar way. <br><br>It would be even better if support could also be provided in Page Wizards for the use of thumbnail images, but I realise that this feature is triggered before a wizard form is opened so may be impractical to implement for Page Wizards.<br><br>So what do people think?<br><br>Would a help-file for each page would be useful?<br><br>From a technical point of view, if the idea is perceived as worthwhile, is it achievable?<br><br>Kind regards<br><br>Johnathan<o:p></o:p></p></div></body></html>