flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: AW: AW: AW: AW: Showcase for IOs and Android skins?
Date Tue, 12 Aug 2014 07:46:07 GMT
But wouldn't using these media queries result in both skin types being compiled into the application?
To me it looks as if this would make the output larger. While this might be good in a web
application, when building Air apps, I usually have to create two output files for iOS and
Android. That's why I was thinking about two packages. But if it's not that much overhead,
your current solution is definitely cooler ;-)

Von: omuppi1@gmail.com <omuppi1@gmail.com> im Auftrag von OmPrakash Muppirala <bigosmallm@gmail.com>
Gesendet: Dienstag, 12. August 2014 01:29
An: users@flex.apache.org
Betreff: Re: AW: AW: AW: AW: Showcase for IOs and Android skins?

On Aug 11, 2014 3:29 PM, "Neverbirth" <neverbirth@gmail.com> wrote:
> >well I fixed some of the problems in the build and created a mobile.swc
> order to use the skins however I needed to duplicate the android4.css file
> as otherwise the normal skins would have been used.
> AFAIK in the final reléase the file should be called default.css

Yes , that is my plan. Although, there is a problem with the AIR simulator
we are trying to work through.  If you can take a look at the thread on dev
and give some ideas, that would be great.

> >How about splitting up the theme into several modules? This way for
> there would be one mobile, mobile-android and mobile-ios theme ... would
> make things a lot easier for the user.
> The expected behaviour would be to have the Android and iOS theme in the
> same SWC, and then use one skin set or the other through media queries,

This is exactly how I had things planned out in my head.


> of course, nothing is written in Stone. I'd expect it to be a swc
> from the current mobile.swc, and then use one or the other through the
> compiler flag.
> --
> View this message in context:
> Sent from the Apache Flex Users mailing list archive at Nabble.com.

View raw message