> The compiler IS the Flex SDK and to empower developers to get involved > would be a huge new driving force for the architecture built to use it. I don't agree with this. I can use the compiler to generate code for a whole new framework if I want to.
>>> Wouldn't it be important if the community had access to the Falcon >>> source at a very early stage? Yes, but the fact is, Adobe is building Falcon for its own commercial reasons and based on this experience as to how distracting it is to donate a project to Apache, it is hard to make an argument that they should risk their schedules to donate early. But we are pushing to find a drop point before they are done. Another thing to keep in mind is that Falcon and its performance improvement is still mainly leveraged by Flash Builder and incremental compiles. The current Flash Builder is not designed to take in a replacement compiler at all so even if you could get the code now, you wouldn't be able to leverage it until long after we want to cut some releases from this project, so I'm trying to make sure folks stay focused on finding key things that will make a difference sooner. A final note: Falcon's MXML handling is still up in the air. The focus is on getting AS compiling as that is the direction of use for Falcon within Adobe. The early drop may not handle MXML at all. On 1/5/12 4:34 AM, "Michael Schmalle" <m...@teotigraphix.com> wrote: > Quoting David Arno <da...@davidarno.org>: > >> +1 >> >>> Wouldn't it be important if the community had access to the Falcon >>> source at a very early stage? >> >> There are some great ideas here around creating an API for the >> compiler to support formatting and documentation tools for example. >> Also I'd like to experiment with adding custom generics support to >> the compiler. I'd love to get involved in this stuff, but see no >> point in starting it with the mxmlc compiler source since we know >> falcon is coming at some point. So please can those with the falcon >> team's ear badger them into releasing to Apache as soon as possible >> (before it's complete.) >> >> David. >> >> > > I will +1 this as well since I will almost certainly be a major > contributor/committer to this branch of development. One of my goals > personally dealing with the Falcon compiler is to create a place that > I will document everything I do as a notepad for others. So I would > like to have as much documentation on the developing the compiler as > say extending a component. > > The compiler IS the Flex SDK and to empower developers to get involved > would be a huge new driving force for the architecture built to use it. > > I see this as a very important step in getting Apache Flex into the > melting pot viewed fairly along side other competing technologies. I > have had a few blog posts about the transformation of Flex and really, > this is exactly where it is going to happen on the low level. > > Mike > > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
