That sounds really promising Dimitri. The French guys to the rescue! :) Having thought about it, I can see why Adobe do not want to donate the compiler to Apache until it's ready. However, they could still provide access to it as you describe before then. The simplest way seems to make use of their existing infrastructure for such things. They could run an open-invite pre-release programme like they do with the runtime and have done with Flash Builder and the SDK in the past. What I think would be really useful to us is if all four of your options were provided via such a pre-release programme. Adobe could push regular update snapshots out that let us experiment with the compiler, as well as letting as look at the code, the APIs and any existing documentation as it develops. Also we would then have a forum of feedback to Adobe.
As long as no non-disclosure agreement got in the way, we could drop plans for an alternative compiler and start work on the MXML and JS stuff within Falcon, whilst Adobe are still developing the core compiler. This would better suite everyone I think. So please do your best to persuade Thibault of this plan. Oh and whilst talking to him, you might want to mention another thing. Months ago, he promised me he'd sort out the fact that Adobe haven't published up to date versions of the AVM2 and SWF specification documents. As mentioned in the "Can Adobe kill Apache Flex" thread, this doesn't appear to have happened... Thanks, David.
