Thanks for the hint, nice to know. However, if and when Falcon will be fully able to compile MXML, how will FB support Apache Flex SDK if it had to bake-in the support for the Adobe's own ASC 2.0 compiler in this way?
Or, maybe, FB will only supports "legacy" MXML compiler when using Apache Flex? (hope not, as this could really slow down Falcon adoption). Just a curiosity, time will tell.. 2013/2/6 Lee Burrows <subscripti...@leeburrows.com> > FB4.7 uses ASC2 by default for pure AS projects but it can be altered by > tweaking config files. > > In .actionScriptProperties file for project, find useFlashSDK="true" and > change to "false". > > > > > On 06/02/2013 12:17, Cosma Colanicchia wrote: > >> Probably OT, but I just read that in FB 4.7 you cannot choose the FDK to >> use for pure ActionScript projects (never tried myself yet). >> >> Does this means that Flash Builder is somewhat hardcoded to work only with >> the shipped ASC 2.0 SDK? If so, I was thinking about implications of this >> when MXML support will be available in Falcon, if it is going to be >> supported in future versions of the IDE. >> >> I know that, before ASC 2.0/Falcon, the FB IDE was doing double work to >> parse source files in order to provide code assist.. I also read that a >> strong point for the architecture behind Falcon is allowing the compiler >> to >> work for the IDE, sharing the AST. >> >> Doing 1+1, I'd say Falcon will improve independence of the IDE from the >> FDK >> versions (as long as these new advanced compiler hook/APIs are keep >> compatible), but this FB 4.7 behavior seems to go in the opposite >> direction.. >> >> Any thoughts? >> >> > > -- > Lee Burrows > ActionScripter > >