<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.htmlpreformattedchar0
{mso-style-name:htmlpreformattedchar;
font-family:Consolas;}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.htmlpreformattedchar00
{mso-style-name:htmlpreformattedchar0;
font-family:Consolas;}
span.balloontextchar00
{mso-style-name:balloontextchar0;
font-family:"Tahoma","sans-serif";}
span.emailstyle22
{mso-style-name:emailstyle22;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle23
{mso-style-name:emailstyle23;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle24
{mso-style-name:emailstyle24;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle25
{mso-style-name:emailstyle25;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle26
{mso-style-name:emailstyle26;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle27
{mso-style-name:emailstyle27;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle28
{mso-style-name:emailstyle28;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle29
{mso-style-name:emailstyle29;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle30
{mso-style-name:emailstyle30;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle32
{mso-style-name:emailstyle32;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle35
{mso-style-name:emailstyle35;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle36
{mso-style-name:emailstyle36;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle37
{mso-style-name:emailstyle37;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle38
{mso-style-name:emailstyle38;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle42
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='color:#1F497D'>‘What you are doing is
asking for trouble.’<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'>I appreciate that, but I’m
stuck between the rock and hard place. For my pilot project I can install on
any convenient webserver, because <i>this_one</i> is for external students (and
I therefore need to build my own thin layers of authentication and storage of
user input), but what I’m really interested in is exploring whether Xerte
could be a good addition to our own bespoke web architecture. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>For historical reasons, this
converts any uploaded files to lower case. To persuade the developers to adjust
this, I’d need to make a compelling use-case, and there’s nothing more
compelling than a practical demonstration which would show how Xerte could add
value (in terms of page level interactivity, and the workflow of academic
end-user using templates that can be mixed with sophisticated interactivity
provided by a specialist) into our own environment. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>So I think some short term hacks
are a reasonable investment (I’m hoping they stop at re-compiling MainPreloader.fla.)<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'>Absolutely no criticism intended
(I’m getting to like Xerte more and more) but would it be a better design
if there were no absolute dependencies on filenames? That’s not particularly
for our own, admittedly very odd situation, but if anyone deployed multiple
xerte learning objects, wouldn’t it make sense to have just a single set
of MainPreloader.swf/ rloObject.js/ XMLEngine.swf etc. that might be housed in
a root directory where path and filenames were kept in an ini file or parameter
to the swf?<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'>Best wishes,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Steve</span><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><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>Julian Tenney<br>
<b>Sent:</b> 17 March 2010 15:34<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> RE: [Xerte] Mixed case dependencies<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>It’s loaded from
MainPreloader.swf.<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'>What you are doing is asking for
trouble.<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"'>
xerte-bounces@lists.nottingham.ac.uk
[mailto:xerte-bounces@lists.nottingham.ac.uk] <b>On Behalf Of </b>Brydges,
Stephen<br>
<b>Sent:</b> Wednesday, March 17, 2010 2:46 PM<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> [Xerte] Mixed case dependencies<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p>
<div id=idOWAReplyText65073>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>I am trying to work within an web
publishing environment that insists on renaming files to convert spaces to
underscores and mixed/uppercase to lowercase. :-(<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>I'm trying to see if it it possible to
change the published Xerte files to conform to that restriction. I can rename:<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>rloObject.js (called within the
index.htm)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>whitePanel.swf (called within the .rlo,
which is editable xml)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>MainPreloader.swf (called within
rloObject.js which is editable)<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>But I also have a XMLEngine.swf - where
does that get called from?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>It is only filenames that are
restricted. Mixed case variable names are no problem.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>Steve<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
</div>
</body>
</html>