> I'm assuming you have some desire to use Falcon. And right now, when you do use Falcon your app spits out those errors. Are you ok with the official answer being "upgrade from 4.10 to 4.11 and/or modify your air-config.xml"?
Until it is well documented or we offer a patch, it seems acceptable to me to agree with. -Fred -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 17 septembre 2013 21:10 À : dev@flex.apache.org Objet : Re: [FALCON] Should Falcon compile older SDKs? On 9/17/13 11:36 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> Erik compiles his AIR app against 4.10 with MXMLC. Works fine. Then >>uses Falcon and gets a bunch of errors about styles only supported in >>Spark theme. The root cause is that the air-config.xml in every >>shipping version of Flex doesn't have a <theme> tag and MXMLC is >>hard-coded to >> assume Spark. Darrell and I would prefer not to hard-code stuff like >> that in Falcon and will change the air-config.xml in 4.11 so if you >>use the Falcon/4.11 combination the app compiles cleanly. If Erik >>doesn't want to upgrade to 4.11, he can add a <theme> tag to his >>SDK's air-config.xml. Are we ok with that? > >I'm not sure what you're saying. If I don't want to upgrade, I'll be >using 'old compiler/4.10', correct? In which case, all will be fine, as >the app compiles fine with those. Or do you mean upgrade to 4.11 but >not to Falcon ('old compiler/4.11')? In which case, how does the 'old >compiler' handle having a default theme added to the AIR config? >I'd guess that it won't mind, correct? I'm assuming you have some desire to use Falcon. And right now, when you do use Falcon your app spits out those errors. Are you ok with the official answer being "upgrade from 4.10 to 4.11 and/or modify your air-config.xml"?
