Alex any movement on this? My hope is still that Adobe will donate this thing and finish development in the open. It would send a strong commitment to Adobe wanting to work with the community.
-----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, January 05, 2012 1:29 PM To: flex-dev@incubator.apache.org Subject: Re: Falcon compiler source code / Falcon architecture The goal is to donate Falcon before it is done, but it won't be before we want to cut some release from our Flex podling. Yes, Falcon looks like it could make your build script run twice as fast, but it won't be the 10x the early prototypes showed for incremental compiles from the tool. One the other hand, MXMLC could compile twice as fast if it was compiling a more modular framework and less stuff to think about. I fully expect Falcon to become available and a major factor in the long run. On 1/5/12 11:19 AM, "Roland Zwaga" <rol...@stackandheap.com> wrote: > From what I remember from the Flex summit talks, there is a fair > chance that Adobe will release the compiler front end earlier than planned. > In that case it would be entirely possible that someone or someones in > the community will build their own MXML frontend into the compiler. > Adobe can still build their own MXML frontend and use it in > Flashbuilder 2012, so they wouldn't necessarily jeopardise their > releases. All in all, they projected they'd have the entire thing > finished in 2013! We really don't want to wait THAT long, with the > community's support this could be sped up quite a bit, plus we'll be > able to build extensions that Adobe hasn't had time to dream up :) The > fact that we can't use the compiler in Flashbuilder also doesn't > concern me too much, if we can hook it up using build scripts I'd be > more than happy to go that route for a while. > So I agree competely with the fact that the new compiler is > potentially a lot more important than the SDK, perhaps not in > short-term, but in the long-run it is going to make all the difference. > > cheers, > > Roland > > > On 5 January 2012 19:17, Michael Schmalle <m...@teotigraphix.com> wrote: > >> Quoting Alex Harui <aha...@adobe.com>: >> >> 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. >>> >>> -- >>> Alex Harui >>> Flex SDK Team >>> Adobe Systems, Inc. >>> http://blogs.adobe.com/aharui >>> >> >> Ok, >> >> Poorly chosen words for exactly what you said. My point is the >> compiler spawns the empowerment I am speaking of, take the Flex SDK >> out of it. My main driving force of understanding is "the thingy that >> reads ActionScript3 source code and puts it into a model AST >> hopefully that a developer like myself could use to create anything". >> >> This parallels what you said Alex, "I can use the compiler to >> generate code for a whole new framework if I want to." >> >> I have been vocal on this because I just can imagine what we can do >> with a pure AS3 model compiled by the Flacon parser. I am not to >> concerned about MXML because that is actually XML that could be >> converted into AST that is used by the actual parser, I have done this in my >> own projects. >> >> I also get that Adobe has plans for it, so I will say no more on this >> topic at this time. >> >> Mike >> >> >> >> >> > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui Notice: This transmission is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. Any dissemination, distribution or copying of this transmission by anyone other than the intended recipient is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by e-mail or telephone and delete the original transmission. Thank you.
