<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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:983503660;
mso-list-type:hybrid;
mso-list-template-ids:-1025460024 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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><i><span style='color:#1F497D'>Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='color:#1F497D'>So there’d be 3 types of links then? One forcing to Flash, one forcing to HTML5 and one deciding for you? Is that going to confuse people as to what link they’re sharing? I agree you need to be able to make manual choice too though.<o:p></o:p></span></i></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I think this kind of depends on the default e.g. right now we obviously have play.php for Flash and play_htm5.php for html 5 <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>If play.php detected for Flash player and if not found reverts to html 5 then perhaps only two links needed like we have now.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I guess if play.php becomes the html 5 view by default then the second link could be play_flash.php which still reverts to html 5 if flash player not found.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Would that work?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><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-dev-bounces@lists.nottingham.ac.uk [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] <b>On Behalf Of </b>Fay Cross<br><b>Sent:</b> 28 March 2013 08:52<br><b>To:</b> For Xerte technical developers<br><b>Subject:</b> [Xerte-dev] Re: HTML5<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Thanks Ron<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='color:#1F497D'>Should there be a separate HTML5 only export option?</span></i><span style='color:#1F497D'><br>That’s what I assumed there would be but I suppose the files could just be added into the existing export with an extra index page<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='color:#1F497D'>Should this be a management option e.g. giving people control over what is the default and what is the Ctrl + Click option?<o:p></o:p></span></i></p><p class=MsoNormal><span style='color:#1F497D'>I like that idea<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='color:#1F497D'>Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5<o:p></o:p></span></i></p><p class=MsoNormal><span style='color:#1F497D'>So there’d be 3 types of links then? One forcing to Flash, one forcing to HTML5 and one deciding for you? Is that going to confuse people as to what link they’re sharing? I agree you need to be able to make manual choice too though.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks for files you sent – I’ll have a look at them in a bit<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><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"'> <a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a> [<a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On Behalf Of </b>Ron Mitchell<br><b>Sent:</b> 27 March 2013 17:57<br><b>To:</b> 'For Xerte technical developers'<br><b>Subject:</b> [Xerte-dev] Re: HTML5<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Hi Fay<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>firstly on behalf of the whole community thanks for all your hard work on all the HTML 5 conversions - fantastic stuff!<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>A few comments/thoughts inline below...<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>HTH<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Ron<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><div><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"'> <a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a> [<a href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On Behalf Of </b>Fay Cross<br><b>Sent:</b> 27 March 2013 17:17<br><b>To:</b> For Xerte technical developers<br><b>Subject:</b> [Xerte-dev] HTML5<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Hello all<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'>As you should know the HTML5 work is nearly complete and there are only a couple of page types for me to complete before we can release a new version of Toolkits with the HTML5 interface as the default view. I have a few things that I could do with some help on before the release so if anyone can give me a hand with them or just give your opinions it would be much appreciated...<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Exporting HTML projects:<br>The files that would need to be in the zip would be more or less the same as for the Flash version but using the common_html5 and models_html5 folders instead of common/models.<span style='color:#1F497D'><br></span><span style='color:red'>Would the easiest way to do this be to include an additional index page e.g. index_html5.htm</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt'><span style='color:red'>Should there be a separate HTML5 only export option?<br>HTML 5 export for vieing locally or importing into a VLE is certainly something people have been asking for</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Abbreviated link:<br>Possibly something Ron can help with as I’ve noticed it’s working on his install. Can abbreviated links be made to work e.g. <a href="http://www.nottingham.ac.uk/toolkits/play_html5_560">www.nottingham.ac.uk/toolkits/play_html5_560</a> rather than using the full url?<br>(Apologies Pat, I think you partly answered this for me previously but I can’t find it)<span style='color:#1F497D'><br></span><span style='color:red'>I've attached a sample .htaccess with most of this included you will need to replace /xerte/ with whatever your xot folder is which you can probably check in your existing .htaccess and just add in the missing lines. However at least some of the rss links need further work which I posted to the list previously but no reply.<br>The htaccess.conf in the setup folder needs updating too but to be honest I'm not sure how that works e.g. if it's updated during install but I don't think it is.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Play / Preview links:<o:p></o:p></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:red'><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Links in project properties, preview button in workspace and preview in wizard need to be updated to go to the HTML5 version.<span style='color:#1F497D'><br></span><span style='color:red'>Should this be a management option e.g. giving people control over what is the default and what is the Ctrl + Click option?<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>In the wizard should Ctrl-Click bring up the Flash version when clicking normally is changed to HTML5?<span style='color:#1F497D'><br></span><span style='color:red'>Yes I think so but see response to a. above</span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:red'><span style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]>Do you think there needs to be some browser detection that decides which version people see? The problem I can see with this is that if we start adding new features or pages to the HTML5 version then by sending them to the Flash version instead they may miss out on some content. Not many of the page types in the HTML5 version actually use HTML5 tags if that makes sense – probably just the handful where the canvas tag is used (textDrawing, charts etc.) so there might not be many instances where there will be problems if you’re on an older browser anyway.<span style='color:#1F497D'><br></span><span style='color:red'>Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt'><o:p> </o:p></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Page models:<o:p></o:p></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>John – is the flickr page finished?<o:p></o:p></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Johnathan – I’ve emailed you off list about a few queries I’ve got with the connector pages, I hope this is ok – I didn’t want to bother everyone else with them<o:p></o:p></p><p class=MsoListParagraph style='margin-left:108.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>c.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>SCORM – this isn’t working at the moment but I can’t quite remember what’s missing. I’ll email with more details of what help I might need when I’ve looked back at it<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Thanks<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>Fay<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><o:p></o:p></span></p></div></body></html>