<HTML dir=ltr><HEAD><TITLE>Re: [Xerte] toolkit on a stick</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16981" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText24851 dir=ltr>
<DIV dir=ltr><FONT size=2>But it looks like Toolkits and Xerte 3 will be the future.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Xerte 2.x isn't going anywhere - in fact I wonder whether Xerte 3 should really be called Xerte 3 as there isn't really an upgrade path for xerte 2 files, and it might just get really confusing. Maybe we need a different name for it to distinquish it. Already, too many people refer to Toolkits as Xerte. Maybe we should rebadge that too. Thinking of names is hard.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Xerte 3 is very much a developer's tool right now, and will be for the foreseeable future, although a Xerte 3 runtime ought to be able to easily consume toolkits data (i.e. xml made with the wizard). The Flex 4 SDK that Xerte 3 is built on is nearly finished now, and will be released shortly by Adobe: Flex 4 is a much richer framework that achieves very similar things to the Xerte 2 framework. The difference is I wrote the Xerte 2 framework, warts and all, whereas Adobe write, maintain, upgrade the Flex 4 SDK - which offers a lot more, and saves me a ton of work. There are many similarities, as Xerte 2 was inspired by a mix of Authorware and Flex.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>I'd really like to get some of you coders playing around with Xerte 3 now, and telling me what you think, what works, what doesn't, what's hard to do that should be easy. We need to start creating some knowledge around it, as it's quite different. There are 63 types of icon, rather than 9, which gives you a good idea of how much richer it is. I imagine a beta lasting most of the rest of this year as you guys start to come to the party.</FONT></DIV></DIV></BODY></HTML>