On Aug 11, 2014 3:29 PM, "Neverbirth" <[email protected]> wrote: > > >well I fixed some of the problems in the build and created a mobile.swc in > 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 example > 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. Thanks, Om but > of course, nothing is written in Stone. I'd expect it to be a swc separated > from the current mobile.swc, and then use one or the other through the theme > compiler flag. > > > > -- > View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Showcase-for-IOs-and-Android-skins-tp7456p7618.html > Sent from the Apache Flex Users mailing list archive at Nabble.com.
