> 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?
> My internal customer's app specifies a long list of locales, including
> en_GB. But they don't have custom resource bundles for en_GB because
> MXMLC will swap in the en_US bundle when it can't find a bundle for en_GB.
> When compiling with Falcon there will be a warning that a locale is
> missing a bundle. Then, if you run against 4.10 or earlier, your app
> won't run because those versions of the SDK require that all locales have
> all of the same bundles, but if you run against 4.11, I'm going to change
> the ResourceManager to ignore missing bundles because the lookup mechanism
> doesn't need it. It is ok with a locale missing a bundle and will search
> for the next locale that has one.
So, you're saying this will only be a problem if you use 'Falcon/4.10'
(new compiler, old SDK). I'd say that isn't a problem, Falcon is new
and should only be 'supported' on new SDKs. Looking forward, not back.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
