|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
|
|
deprecation of ColorSchemes preference moduleHi all,
with the development of Themes, ColorSchemes are a bit obsolete: A theme contains all the color specifications a COlorScheme can do and much more. Of course color schemes continue to work and be available. Currently ColorSchemes can be managed with the ColorSchemes module in SystemPreferences (or by the equivalent module of the Preferences app in Backbone). I am creating right these days a new Module for SystemPreferences which allows the managment of installed Themes. It works like the current theme selection scheme which is per-application in the Info Panel, but in this case the module writes in the global domain. Essentially it is a user-friendly way to set "NSGlobalDomain GSTheme myTheme". I think this is truly needed for user-friendlyness in a GNustep workspace. Now I think that the color schemes module is obsolete and superseded and that having both causes confusion. I propose do deprecate it, that is, leave it there, but just don't build it and install it by default when building SystemPreferences and build+install the Themes one instead. What do you think of that? Riccardo _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@... http://lists.gnu.org/mailman/listinfo/discuss-gnustep |
|
|
Re: deprecation of ColorSchemes preference moduleOn Wed, Oct 28, 2009 at 7:47 PM, Riccardo Mottola <multix@...> wrote:
> Hi all, > > with the development of Themes, ColorSchemes are a bit obsolete: A theme > contains all the color specifications a COlorScheme can do and much more. Of > course color schemes continue to work and be available. > > Currently ColorSchemes can be managed with the ColorSchemes module in > SystemPreferences (or by the equivalent module of the Preferences app in > Backbone). > > I am creating right these days a new Module for SystemPreferences which > allows the managment of installed Themes. It works like the current theme > selection scheme which is per-application in the Info Panel, but in this > case the module writes in the global domain. > > Essentially it is a user-friendly way to set "NSGlobalDomain GSTheme > myTheme". I think this is truly needed for user-friendlyness in a GNustep > workspace. > > Now I think that the color schemes module is obsolete and superseded and > that having both causes confusion. > > I propose do deprecate it, that is, leave it there, but just don't build it > and install it by default when building SystemPreferences and build+install > the Themes one instead. > > What do you think of that? +1, go for it. -- Nicolas Roard "I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@... http://lists.gnu.org/mailman/listinfo/discuss-gnustep |
| Free embeddable forum powered by Nabble | Forum Help |