I'm not familiar with the code but it makes sense to abstract away visual styles so that custom themes/styles can be easily swapped out. Especially when you consider how frequently design styles are changing, like how the flat UI theme was so amazing and now, if you follow threads on dribbble, you'll see people are bored to death and tired of it. Also as an example, the original flash/flex component styles used lots of gloss and embossing, a style that really started to fade out years ago.
It would make for easy user customization which would obviously make the whole framework more appealing. Take XAML for example. I can download something like Mahapps.Metro and by simply changing 1 line in my XAML window declaration, all of my components and window itself become completely restyled. On Tue, Dec 9, 2014 at 1:41 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > On Tue, Dec 9, 2014 at 10:29 AM, Subscriptions < > subscripti...@leeburrows.com > > wrote: > > > Perhaps sdk could include 2 mobile theme SWCs (one with new stuff, one > > without)? Then users who dont want to update could use the legacy theme > (in > > same way we currently select any alternative theme). > > > > > We discussed this and decided not to go with a separate theme/swc. This > felt like the right decision at that time. > > > > Should be straight-forward to update the build script to generate both > > SWCs (which i'm happy to do if its agreed that its the best solution) > > > > Can you provide a patch? We can see how it affects the workflow and how > easy/hard it is for users. We should probably discuss your proposed > workflow in this thread first before you start working on it. > > Thanks, > Om > > > > > > Lee Burrows > > ActionScripter > > > > > > On 09/12/2014 18:13, OmPrakash Muppirala wrote: > > > >> I want to point out that the new skins will show up only for Android OS > > > >> 4.0 and iOS > 7. If an older OS is detected, the old skins show up. > >> > >> That said, we can add a mechanism to turn it off. What is your usecase? > >> What would be a good way, in you mind to turn off the new skins? A > >> compiler directive? Anything else you can think of? > >> > >> As an easy workaround, you can simply copy the 4.13's > >> mobiletheme/default.css into your local source directory and use that > >> stylesheet. All the old skins should show up. > >> > >> Thanks, > >> Om > >> > >> On Tue, Dec 9, 2014 at 9:36 AM, Subscriptions < > >> subscripti...@leeburrows.com> > >> wrote: > >> > >> I do not like the sound of that!!! > >>> > >>> How do i turn off the new skins? > >>> > >>> Lee Burrows > >>> ActionScripter > >>> > >>> > >>> On 09/12/2014 17:29, OmPrakash Muppirala wrote: > >>> > >>> And since we are issued CSS selectors, you don't have to > >>>> change anything in your code. The new skins should just show up on > your > >>>> device when you recompile the app. > >>>> > >>>> > >>> > > > -- Jesse Nicholson
