While we're on the subject, I learned a few things in my meetings today that may not have occurred to folks wanting to change the compiler and language.
1) Falcon is intended to serve not only as the compiler for FB, but as the code-model service for FB's code intelligence. 2) The version of FB that integrates Falcon will not be designed to use a different version of Falcon for different versions of the SDK. This is different than today, where FB uses the MXMLC from the SDK version for your project. This has some interesting implications. One is that we can't keep rolling out new versions of Falcon without factoring in backward compatible MXML code-gen for older SDKs. Another is that, if you muck with the language, the code-intelligence in FB will break or at minimum, won't be able to assist in those new language constructs. For the first issue, the plan of record was to have Falcon convert MXML constructs to data structures instead of code, and modify the SDK framework to interpret those data structures. That work will likely not be fully complete at the time of donation. Anyway, keeps these facts in mind as you plan the future for Falcon. -Alex On 1/17/12 2:37 PM, "Jonathan Campos" <jonbcam...@gmail.com> wrote: > On Tue, Jan 17, 2012 at 4:35 PM, Roland Zwaga <rol...@stackandheap.com>wrote: > >> I agree, sorry if I sounded impatient :) And I understand the legal battles >> that Alex et al have to wage >> to get the code out there earlier than the original timeline. >> > > "Soon" can't be soon enough in my book. The earlier the better. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
