A summary of what I did and why: I have created a whole bunch of Android 4.x specific skins. I am enabling these skins by default when I detect Android with a version of greater than 4. This is achieved through the new os-platform and min-os-version media query selectors. This works fine when running on a device.
But on the AIR Simulator (ADL) we are not able to calculate the min-os-version because that is not set anywhere. So, I have added a new Mixin class AndroidPlatformVersionOverride that sets the required Android os version that the user wants to test on. To enable this mixin, the user needs to add this to their compiler options: -includes=mx.utils.AndroidPlatformVersionOverride This triggers the mixin to set the required Android OS version which in turn ensures that the CSS MediaQueryParser is able to understand the user's intentions of using Android specific skins and display it correctly on the AIR simulator. Thanks, Om On Wed, Aug 13, 2014 at 1:53 AM, OmPrakash Muppirala <[email protected]> wrote: > I just checked in this functionality. Please do a quick review when you > get a chance. > > Thanks, > Om > > > On Tue, Aug 12, 2014 at 1:36 PM, Alex Harui <[email protected]> wrote: > >> >> >> On 8/12/14 11:42 AM, "OmPrakash Muppirala" <[email protected]> wrote: >> >>It seems like that would be useful for testing different versions of >> >> Android in the simulator regardless of this bug. >> >> >> > >> >There is another problem though. I have a mobile app with two run/debug >> >configurations, one for iOS and one for Android. AIR simulator works >> fine >> >for iOS, i.e. it does correctly report "IOS xxx" for version. >> > >> >If I add this as a compiler option, it will apply to all run >> >configurations, right? Is there a way to include a compiler option for a >> >particular run configuration in FB? >> Well, you could have the Mixin check the other Capabilities properties and >> decide whether to apply the override or not. >> >> -Alex >> >> >
