Comments on: Squib of the day: named colours http://blogs.gnome.org/metacity/2009/03/27/squib-of-the-day-named-colours/ "Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." Sun, 26 Sep 2010 15:08:40 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Screwtape http://blogs.gnome.org/metacity/2009/03/27/squib-of-the-day-named-colours/comment-page-1/#comment-947 Screwtape Fri, 27 Mar 2009 03:38:10 +0000 http://blogs.gnome.org/metacity/?p=548#comment-947 It's not really obvious exactly what the original bug filer wanted his Metacity themes to match. Matching various colours in the active GTK+ theme is <a href="http://screwtape.jottit.com/colours_in_metacity_themes" rel="nofollow">pretty easy</a>, although I don't believe you can access <a href="http://live.gnome.org/GnomeArt/Tutorials/GtkThemes/SymbolicColors" rel="nofollow">GTK+ symbolic colours</a> which might possibly be useful (I believe this is how the colour-pickers in Ubuntu's GTK theme editor work). Alternatively, if the idea is to have multiple themes with the same base design and different accent colours, I think a better approach would be to add separate sub-theme files that allow colour-constants to be overridden. You could add a 'subtheme' gconf key in parallel to the existing 'theme' key, and older themes with no sub-themes would just ignore it. Likewise, older Metacity versions would ignore the sub-theme files in newer themes so compatibility would be preserved. Another possibility is that this bug can be marked FIXED by the addition of colour constants to the V2 theme format - or even by the "colorize" attribute on the image draw_op. It’s not really obvious exactly what the original bug filer wanted his Metacity themes to match. Matching various colours in the active GTK+ theme is pretty easy, although I don’t believe you can access GTK+ symbolic colours which might possibly be useful (I believe this is how the colour-pickers in Ubuntu’s GTK theme editor work).

Alternatively, if the idea is to have multiple themes with the same base design and different accent colours, I think a better approach would be to add separate sub-theme files that allow colour-constants to be overridden. You could add a ‘subtheme’ gconf key in parallel to the existing ‘theme’ key, and older themes with no sub-themes would just ignore it. Likewise, older Metacity versions would ignore the sub-theme files in newer themes so compatibility would be preserved.

Another possibility is that this bug can be marked FIXED by the addition of colour constants to the V2 theme format – or even by the “colorize” attribute on the image draw_op.

]]>