>Right, it would be not all that easy, but the current situation is a >little too restricting. Maybe you'd like Thinice in beige shades. Well, >unless you know how to edit the gtkrc (and that there is such thing as >the gtkrc) you can't do that. You could on the other hand take a little >time and select some custom colors. With an instant preview of your >selection in a small preview-pane, this is very handy. Many themes come >in different color schemes, that would after all be superfluously with >an editable palette. You could OTOH still ship them... just by making >some more palettes available.
Agreed, but it's not a task of gtk to provide application for rc files editing. That can be part of gnome-themes or something like this. The task of gtk is to provide underlying framework. >Now, firstly as I said above, I'd like to seem them as a whole sale >replacement, to be edited by the users, if they wish. Furthermore, there >is no point in defining >stock_color["evolution-important-mail"] = "#a5a5a5a" >after all we're heading for more consistency. Therefore defining a >separate color for evolution would just be counterproductive, imho. It >should be >stock_color[IMPORTANT] = "#F03333" Sure :). When writing the example above I was thinking about the ability of applications to add their custom stock colors. There is no problem since evolution also adds many stock icons to default gtk set. While looking at all this, I've created test implementation of stock colors. Patch to gtk 2.6.4 is attached to bug http://bugzilla.gnome.org/show_bug.cgi?id=114355 One can see it in action with test/teststockcolor. So I am waiting for futher comments, the most important is the exact list of default stock colors and their values. _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list