On Sep 17, 2013 12:22 PM, "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"?
>
> Certainly. If I want to use the new compiler, it's not unreasonable to
> expect of me that I use a new SDK as well.
I am not sure what exactly the benefits are when switching to the new
Falcon compiler. Why exactly would I go through the hassle of modifying
all these?
I think Alex mentioned a while ago that we cannot expect compile times to
improve a lot with Falcon. Am I mistaken?
If it is tied to a new SDK at least, it makes sense.
Thanks,
Om
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
