Hi, I agree that there should be only one, platform independent look-and-feel. I think the goal of such a theme would be to be slick and fast.
Now, regarding the GLMOrangeTheme, the name is a bit confusing because the theme does a bit more than just setting a color. I like the idea of settings, and I will try to make the Glamorous Theme use it. Cheers, Doru On 14 Jan 2011, at 00:58, Igor Stasenko wrote: > On 13 January 2011 21:57, Alain Plantec <[email protected]> wrote: >> Hi all, >> yes, I agree >> >> list selection and selection colors (and some others) can be changed from >> the setting browser. >> I think that in the core only the default theme should be present. >> The others should be packaged separately and loadable on-demand or >> when a package is loaded as it is for moose/glamour. > > +1 > i think we should get rid of all themes and leave only single default one. > > Actually today i was attempting to make sure that orange could be turned into > any other color of choice by picking a different color in settings. > Unfortunately its not so easy, because some widget do not honor / > using theme settings correctly. > > And theme by itself not always honors the settings. > > As a wish for future, i think we should fold all UI settings under a > per-theme settings, > so when user selects a concrete UI theme, then theme could control, > which UI Settings > it makes public and this allows to be modified, and which are not, and > should always use built-in (like window color or icons). > > Then theme could control whether it supports changing particular setting or > not. > For instance i could use single color (orange) to define colors for > multiple things: > - Menu selection color > - Find replace selection color > ... others > > and to user show only 'Selection color' > > > >> Cheers >> Alain >> > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "Beauty is where we see it."
