Thanks Gordon for giving us some hints about Falcon's roadmap. Good luck to you and your team and lets hope falcon's quality will reach at the developers expectation.
On Thu, Feb 16, 2012 at 6:00 PM, Gordon Smith <gosm...@adobe.com> wrote: > > Falcon ... will support AS3 only, with no support for MXML. > > This is incorrect. > > Falcon *already* supports enough of MXML to compile a correctly-running > version of Checkinapp, the test app that is part of the SDK. Falcon's > support for .mxml, .css, and .properties still needs lots of polish -- > especially in the areas of databinding, states, and MXML-specific error > reporting -- but at least 80% of the this work is complete. > > What the whitepaper is really trying to say is that the AS part of Falcon > will be shipping quality while the rest may be more like alpha quality. > > - Gordon Smith, Falcon team > > > -----Original Message----- > From: David Arno [mailto:da...@davidarno.org] > Sent: Thursday, February 16, 2012 2:39 AM > To: flex-dev@incubator.apache.org > Subject: Time for an Apache Flex compiler. > > Yesterday Adobe published their "whitepaper" on the future of Flex. In it, > they state that they'll be contributing the Falcon compiler to Apache > sometime between October and December. This compiler will support > AS3 only, with no support for MXML. So when we get the compiler (which as > already slipped from a summer - according to Alex I think - to winter > release,) we will then need to get our heads around how it works and then > add MXML support before we can use it as a replacement to the mxmlc and > compc compilers. > > This is not a viable timescale for Apache Flex in my opinion. Therefore I > feel we have no choice but to ignore Falcon and to start developing our own > compiler with immediate effect. I therefore want to get an idea as to who, > if anyone, here is interested in getting involved in this initiative? > > David. > > >
