[svn] 2594: For the following:

Question

Revision: 2594<br />Author:   [email protected]<br />Date:     2008-07-23 11:41:51 -0700 (Wed, 23 Jul 2008)<br /><br />Log Message:<br />-----------<br />For the following:<br /><br />  <?xml version="1.0" encoding="utf-8"?><br />  <mx:Application xmlns="http://ns.adobe.com/mxml/2009" xmlns:mx="library:adobe/flex/halo"><br />    <Graphic ><br />      <Model/><br />    </Graphic><br />  </mx:Application><br /><br />Two initializers were being created.  One for the top level variable,<br />created via ModelBuilder's registerModel() call.  The other for the<br />Graphic.content default property.  Both initializers were creating a<br />RHS initializer function, which was causing a duplicate function<br />error.  This fix just suppresses the creation of the top level<br />variable and it's associated initializer, if the Model isn't toplevel.<br />I suspect no one has run into this before, because most visual<br />components don't have an untyped property, which is set to a Model.<br />Very rare edge case.<br /><br />tests Passed: checkintests<br /><br />Needs QA: YES<br /><br />Needs DOC: NO<br /><br />Bug fixes: SDK-16039<br /><br />API Change: NO<br /><br />Reviewer: clucier<br /><br />Code-level description of changes:<br /> <br />  DocumentBuilder.java<br /><br />    Modified ModelBuilder constructor call to pass in null for the parent.<br /><br />  ModelBuilder.java<br /><br />    Added parent variable and modified constructor to set it.<br /><br />    Modified analyze(ModelNode) to pass in (parent == null) for the<br />    toplevel param of registerModel().<br /><br />  AbstractBuilder.java<br /><br />    Modified ModelBuilder constructor call to pass in model for the parent.<br /><br />Ticket Links:<br />------------<br />    http://bugs.adobe.com/jira/browse/utf-8<br />    http://bugs.adobe.com/jira/browse/SDK-16039<br /><br />Modified Paths:<br />--------------<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ModelBuilder.java

Answer 1

Based on the current benchmarks and reviews, I would say the MBA could +in theory+ do all that, but I think you would be highly disappointed with its performance. You may be ok if you did only one of the things you listed at a time, but I'm getting the feeling that this isn't the way you would like to use your notebook.
The biggest weakness of the MBA is the inability to upgrade the RAM beyond 2GB, as well as the slower parallel ATA interface the HDD uses. Bottom line - the MBA wasn't really designed for anything beyond light use (writing, note taking, email, web browsing) But if portability>performance (for you), then I'd suggest seeing how the MBA fares by heading down to an Apple Store and putting one through its paces before committing to buying one.
I just see so many posts here where people with a laundry list of expectations from a notebook are ready to drop ~$1800 for an MBA when from a practical standpoint, that kind of money would be better spent on a higher performing MB or MBP. (IMO)
Message was edited by: Shaggywerewolf