Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.191 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Sun, 19 Feb 2012 11:27:42 -0800
Subject: Re: Adobe / Apache / Spoon Flex Tour
Thread-Topic: Adobe / Apache / Spoon Flex Tour
Thread-Index: 
 AQHM7nZImif9ZJNNQ+uoBsZG/LvpB5ZEYYGAgAAG8oCAABwmAIAAUHKA//+jXgCAAGW6AP//n2JwgAAep94=
Message-ID: <CB668D2E.3C39F%aharui@adobe.com>
In-Reply-To: 
 <EB6F7A48D477254EAB8F675582F80CD712BEF1@DPSBS1.digitalprimates.local>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 2/19/12 9:39 AM, "Michael A. Labriola" <labriola@digitalprimates.net>
wrote:

>> I believe Gordon Smith said in one of the email threads that the new com=
piler
>> is no longer generating ActionScript 3 from the MXML files but convertin=
g
>> directly to bytecode. I would imagine this is the preferred >approach, n=
o? I
>> haven't done any compiler dev myself, yet... but I'm eager to learn.
>=20
> IMO, no. I think, although the structure was wrong, the approach taken in=
 the
> Flex 3.x timeline where MXML was nothing but a set of descriptors was muc=
h
> better.
>=20
> I like to think of MXML as declarative configuration for my project's vie=
ws.
>=20
Well, even the descriptors have to be described in bytecode, and Falcon goe=
s
straight to the equivalent bytecode instead of an intermediate step of
generated AS.

I implemented a new descriptor system for both MX and Spark components in
Falcon, but it needs vetting and testing.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui