Comments on: Apologia for CSS http://blogs.gnome.org/metacity/2009/07/20/apologia/ "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: Arc http://blogs.gnome.org/metacity/2009/07/20/apologia/comment-page-1/#comment-1088 Arc Mon, 27 Jul 2009 17:29:32 +0000 http://blogs.gnome.org/metacity/?p=633#comment-1088 That Anon speaks wisely. Also, add a dialog akin to what's available in Firefox (and most other browsers?). '' Preferences >> Content >> Fonts & Colors >> Advanced >> Allow pages (themes!) to choose their own fonts, instead of my selections above. '' Or you could make theming modular if you want to get advanced. Instead of having one 'do it all theme', allow users to have a list of CSS files/packages as an 'advanced' setting. Of course you would have to add some form of warning dialog about the possibility of problems. That Anon speaks wisely. Also, add a dialog akin to what’s available in Firefox (and most other browsers?).
” Preferences >> Content >> Fonts & Colors >> Advanced >> Allow pages (themes!) to choose their own fonts, instead of my selections above. ”

Or you could make theming modular if you want to get advanced. Instead of having one ‘do it all theme’, allow users to have a list of CSS files/packages as an ‘advanced’ setting. Of course you would have to add some form of warning dialog about the possibility of problems.

]]> By: Anonymous http://blogs.gnome.org/metacity/2009/07/20/apologia/comment-page-1/#comment-1087 Anonymous Tue, 21 Jul 2009 14:27:52 +0000 http://blogs.gnome.org/metacity/?p=633#comment-1087 Why not take advantage of the C in CSS: allow users to override theme settings by way of a user stylesheet which overrides the theme stylesheet? Why not take advantage of the C in CSS: allow users to override theme settings by way of a user stylesheet which overrides the theme stylesheet?

]]> By: Thomas Thurman http://blogs.gnome.org/metacity/2009/07/20/apologia/comment-page-1/#comment-1084 Thomas Thurman Mon, 20 Jul 2009 19:52:20 +0000 http://blogs.gnome.org/metacity/?p=633#comment-1084 @Lubomir: Certainly there are many good reasons not to let themes dictate the font. Thank you for a good example of one! I'm not sure whether there's a middle ground. Perhaps it would be safe to let them suggest a font and have the default being to override it. Perhaps it would be safe to let them choose serif/sans-serif etc but not the actual font name. @Lubomir:

Certainly there are many good reasons not to let themes dictate the font. Thank you for a good example of one!

I’m not sure whether there’s a middle ground. Perhaps it would be safe to let them suggest a font and have the default being to override it. Perhaps it would be safe to let them choose serif/sans-serif etc but not the actual font name.

]]> By: Lubomir http://blogs.gnome.org/metacity/2009/07/20/apologia/comment-page-1/#comment-1083 Lubomir Mon, 20 Jul 2009 19:35:07 +0000 http://blogs.gnome.org/metacity/?p=633#comment-1083 Please, be careful about allowing theme designers to set the font of the titlebar. I am pretty sure some of them will use fonts that do not contain non ascii letters and this will make some themes unusable for certain users. For example right now 3 of my 10 currently opened windows have Czech characters in title. Please, be careful about allowing theme designers to set the font of the titlebar. I am pretty sure some of them will use fonts that do not contain non ascii letters and this will make some themes unusable for certain users. For example right now 3 of my 10 currently opened windows have Czech characters in title.

]]>