<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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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;}
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";}
p.ecxmsonormal, li.ecxmsonormal, div.ecxmsonormal
{mso-style-name:ecxmsonormal;
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";}
p.ecxmsolistparagraph, li.ecxmsolistparagraph, div.ecxmsolistparagraph
{mso-style-name:ecxmsolistparagraph;
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";}
span.ecxmsohyperlink
{mso-style-name:ecxmsohyperlink;}
span.ecxmsohyperlinkfollowed
{mso-style-name:ecxmsohyperlinkfollowed;}
span.ecxemailstyle17
{mso-style-name:ecxemailstyle17;}
p.ecxmsonormal1, li.ecxmsonormal1, div.ecxmsonormal1
{mso-style-name:ecxmsonormal1;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxmsohyperlink1
{mso-style-name:ecxmsohyperlink1;
color:blue;
text-decoration:underline;}
span.ecxmsohyperlinkfollowed1
{mso-style-name:ecxmsohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
p.ecxmsolistparagraph1, li.ecxmsolistparagraph1, div.ecxmsolistparagraph1
{mso-style-name:ecxmsolistparagraph1;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxemailstyle171
{mso-style-name:ecxemailstyle171;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{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;}
-->
</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'>Xerte Pro<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Xerte 3.0<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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>Dave Burnett<br>
<b>Sent:</b> 11 October 2010 13:39<br>
<b>To:</b> Xerte list<br>
<b>Subject:</b> RE: [Xerte] Xerte 3.0 Beta<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='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:36.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:red'>M</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>xml
<span style='color:red'>E</span>ditor <span style='color:red'>T</span>rue <span
style='color:red'>O</span>bject <span style='color:red'>O</span>rientation<br>
<br>
:)<br>
<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='margin-left:36.0pt;text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:36.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:
Julian.Tenney@nottingham.ac.uk<br>
To: xerte@lists.nottingham.ac.uk<br>
Date: Mon, 11 Oct 2010 10:12:37 +0100<br>
Subject: RE: [Xerte] Xerte 3.0 Beta<o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>This is the change I alluded
to. Changing the software to compile swfs rather than interpret .xml at runtime
to create the content means changing the file format: there are a load of good
reasons to do this, and some recent changes to Air that made it possible:</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Air 2.0 allows communication to native processes. This means
Xerte can communicate directly with fcsh.exe in the FlexSDK to compile the
swfs, and also to the debugger. This wasn’t possible with Zinc or older
versions of Air.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The interpreted code was slow. Compiled swfs are much much much
faster.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Interpreted code still didn’t allow true functions to be
created. You could use the function keyword to create pseudo functions, but
they weren’t of the type ‘function’ and couldn’t be passed as properties to
components; this was particularly troublesome for event handlers;</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It was very difficult / impossible to create new classes at
runtime. Any component property that needs a class (like an icon on a tab bar)
needed a fiddly workaround, nd iti didn’t work in all cases;</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Style sheets needed compiling with the Flex SDK. Now inline
styles can be defined and compiled directly into the swf;</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Extending with your own classes was more difficult than it needed
to be. This still needs a bit of work, but you’ll be able to add your own
classes, written in AS3 to the application.</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You can now use all the skinning stuff to create your own skins,
and Xerte can create / edit skins. I’ve an example, but this is pretty nifty.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You have support for states that are much better managed in
.mxml than ActionScript. States are also pretty nifty.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You’ll be able to use components from the vast array of Flex
resources out there;</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You’re no longer dependent on my runtime. This means less work
for me, and means that all the existing Flex books / tutorials / resources are
relevant to you. Xerte is essentially now an .mxml editor. You are getting into
a very marketable and transferable set of knowledge and skills;</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It will be much easier to keep up with future changes to the
Flex SDK. This is another big weight off my mind / desk.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>The older files more or less
translate, as the xml had initialisation info for each component in it, so
<ButtonIcon…/> is much the same as <Button…/></span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I think the changes are well
worth it.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>J</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='margin-left:72.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> 09 October 2010 21:44<br>
<b>To:</b> Xerte discussion list<br>
<b>Subject:</b> Re: [Xerte] Xerte 3.0 Beta</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Congratulations on your new version of Xerte
3.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>I have downloaded and installed the new
version, but find that it will not open any of the examples that you created
for the earlier version of Xerte 3.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>It looks very interesting, I am looking
forward to the tutorials.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Kind regards<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Johnathan<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>On 7 October 2010 14:02, Ron Mitchell <<a
href="mailto:ronm@mitchellmedia.co.uk">ronm@mitchellmedia.co.uk</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:11.0pt;
font-family:"Tahoma","sans-serif";color:#1F497D'>Brilliant! Wish I had time to
play. </span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:11.0pt;
font-family:"Tahoma","sans-serif";color:#1F497D'>Congrats to all involved.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:11.0pt;
font-family:"Tahoma","sans-serif";color:#1F497D'> </span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='margin-left:72.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-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a>
[mailto:<a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a>]
<b>On Behalf Of </b>Dave Burnett<br>
<b>Sent:</b> 07 October 2010 13:50<br>
<b>To:</b> Xerte list<br>
<b>Subject:</b> RE: [Xerte] Xerte 3.0 Beta</span><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:72.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
Kudos to all involved.<br>
A major undertaking.<br>
<br>
Dave<o:p></o:p></span></p>
<div style='margin-left:36.0pt'>
<div class=MsoNormal align=center style='margin-left:36.0pt;text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=3 width="100%" align=center>
</span></div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:72.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:
<a href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a><br>
To: <a href="mailto:xerte@lists.nottingham.ac.uk">xerte@lists.nottingham.ac.uk</a><br>
Date: Thu, 7 Oct 2010 13:41:42 +0100<br>
Subject: [Xerte] Xerte 3.0 Beta<o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Hi,<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>There is a new beta of Xerte 3.0 to play
with that you can download here: <a
href="http://www.nottingham.ac.uk/xerte/xerte3.htm" target="_blank">http://www.nottingham.ac.uk/xerte/xerte3.htm</a>.
Xerte 3.0 is a complete rewrite of Xerte 2.x, using the Flex framework. There
is a major difference between this latest version and previous versions which I
wanted to say something about. Anyone following Xerte 3.0 developments, or
starting to use Xerte 3.0 to develop content needs to be aware of these
changes.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
Xerte 3.0 now compiles .swf files. It creates, from your code, the actual .swf
file. There is no engine.swf unlike previous versions of Xerte 3.0 and Xerte
2.x. There are a number of good reasons why this was a good step to take. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Xerte 3.0 is really an .mxml editor and
compiler using the Flex SDK to compile.swfs. You will need to download and
install the Flex SDK to use Xerte 3.0 (see instructions on the web site). This
means that Xerte 3.0 is quite clearly a tool for developers. It also means that
you are interacting with the Flex SDK directly, rather than having our code
parse and play your code. There are major performance benefits to doing this,
as well as getting access to all the benefits of the Flex SDK, and it means
that you can directly draw on all the Flex community’s knowledge to create
content with Xerte 3.0. Xerte 3.0 can compile many of the examples on Adobe’s
website and in the help system, as well as dozens of samples already available
from the Flex community. It also means you are developing marketable skills in
an established software development environment.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Flex is a very powerful, flexible (pardon
the pun) and extensible suite of tools. Xerte 3.0 aims to fill a gap in the
market of tools that sits somewhere between the hardcode coder’s IDEs such as
FlashDevelop or FlashBuilder, and something like Xerte 2.x or Authorware, and
as time goes on Xerte 3.0 will contain more and more elearning specific
features.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Xerte 3.0 can build ‘normal’ flash
applications. It can also build Air applications, and package them into
installers, and when the Flex 4.5 SDK is complete, Xerte 3.0 will be able to
build Mobile Applications. Being able to target all these platforms is
exciting, particularly the mobile Air applications. Xerte 3.0 development is
now closely following the development of the Flex 4.5 SDK – when that is
complete I’ll be able to finish Xerte 3.0 and draw on all the new features in
Flex 4.5.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>There’s loads more to say about Flex, but
not enough time or space here. I’m going to start a series of short tutorials
to introduce you to the new environment and features, and walk you through all
the new components, and other stuff you’ll want to know about: components,
styles, skinning, states, effects, transitions, data binding, using your own
custom classes…<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>In the meantime, download and install the
beta, and let me know any comments,<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Thanks to Peter Huppertz - who has made a
major contribution,<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Have fun.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>J<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
This message and any attachment are intended solely for the addressee and may
contain confidential information. If you have received this message in error,
please send it back to me, and immediately delete it. Please do not use, copy
or disclose the information contained in this message or in any attachment. Any
views or opinions expressed by the author of this email do not necessarily
reflect the views of the University of Nottingham. <br>
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. <br>
<br>
_______________________________________________ Xerte mailing list <a
href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a> <a
href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a>
This message and any attachment are intended solely for the addressee and may
contain confidential information. If you have received this message in error,
please send it back to me, and immediately delete it. Please do not use, copy
or disclose the information contained in this message or in any attachment. Any
views or opinions expressed by the author of this email do not necessarily
reflect the views of the University of Nottingham. 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. <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:
12.0pt;margin-left:72.0pt'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br>
_______________________________________________<br>
Xerte mailing list<br>
<a href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a><br>
<a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a><br>
<br>
This message and any attachment are intended solely for the addressee and may
contain confidential information. If you have received this message in error,
please send it back to me, and immediately delete it. Please do not use,
copy or disclose the information contained in this message or in any
attachment. Any views or opinions expressed by the author of this email
do not necessarily reflect the views of the University of Nottingham.<br>
<br>
This message has been checked for viruses but the contents of an attachment<br>
may still contain software viruses which could damage your computer system:<br>
you are advised to perform your own checks. Email communications with the<br>
University of Nottingham may be monitored as permitted by UK legislation.<o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
_______________________________________________ Xerte mailing list
Xerte@lists.nottingham.ac.uk http://lists.nottingham.ac.uk/mailman/listinfo/xerte
This message and any attachment are intended solely for the addressee and may
contain confidential information. If you have received this message in error,
please send it back to me, and immediately delete it. Please do not use, copy
or disclose the information contained in this message or in any attachment. Any
views or opinions expressed by the author of this email do not necessarily
reflect the views of the University of Nottingham. 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. <o:p></o:p></span></p>
</div>
</body>
</html>