OSD symbols

Kenneth Wimer kwwii at sinecera.de
Wed Dec 2 08:11:42 PST 2009


On Wednesday 02 December 2009 04:05:59 pm Ted Gould wrote:
> On Wed, 2009-12-02 at 09:42 -0500, Matthias Clasen wrote:
> > On Wed, 2009-12-02 at 15:14 +0100, Jakub Steiner wrote:
> > > On Wed, Dec 2, 2009 at 3:00 PM, Patryk Zawadzki <patrys at pld-linux.org> 
wrote:
> > > > To do it properly you'll need a "glyph" drawing mode for icons.
> > > >
> > > > https://bugzilla.gnome.org/show_bug.cgi?id=591698
> > >
> > > Perhaps that is indeed the way to go. I would have personally thought
> > > injecting a stylesheet "path { fill: #fff }" where the color would be
> > > taken from text[NORMAL] or somesuch would be more appropriate? This
> > > would enable us to color a specific part of the symbol differently
> > > (think about a last bar of battery-critical). Just have that part of
> > > the SVG labeled 'warning' and then do something like
> > > "path[inkscape:label='warning'] { fill: #f00 } where that would be
> > > mapped from gtkrc (either a new named color @warning or
> > > @selected_fg_color).
> >
> > I don't think anything replacing individual colors is going to work very
> > well in general. I was thinking you'd probably have to do something the
> > color rotation in the gimp: convert to hls, rotate to map hue in icon to
> > hue of theme color, then convert back. That would let you have 'red' as
> > alert color in your icon and e.g. purple in the theme, and let you map
> > all shades of red in the icon to shades of purple.
> 
> I strongly believe that we shouldn't do any automatic choosing of color,
> and just allow the theme to set symbolic color names that are passed
> into the SVG as named colors.  So a theme could set a "warning_color"
> and adjust that based on what colors work.  Computers suck at choosing
> colors and there becomes a11y issues as well.
>
> I think the basis for this discussion was put here by Matthew Paul
> Thomas:
> 
>   http://www.freedesktop.org/wiki/SymbolicIcons
> 
> But we had discussed the idea of substituting the colors at UDS, and I
> think it's a worthwhile investigation.
> 
> If it is reasonable, I think we should standardize a set of "expected"
> names for icon authors.  I'm thinking like "text_color",
> "background_color" and "prelight_color" or some such.

Most important will be the foreground colors like normal, prelight, active, 
selected and insensitive.

How many other colors are needed? Warning/Failure, Success/Completion/New are 
two that come to mind.

Do we need to consider animations (network manager comes to mind)?

--
Kenneth


More information about the xdg mailing list