From: Andreas K. <and...@ac...> - 2009-02-11 18:26:05
|
Joe English wrote: > Andreas Kupries wrote: Side note: And what a nice response to something I just hacked together in half an hour, on the side, for use in a private app. :D Seems I poked an area of (very) high interest. >> From the quick look ICONS has at least one thing Jeff wants and I had not >> cared about in my famfam packages ... Multiple themes, and standard icon name >> s across themes. > > Some other notes: Thanks. > The fd.o spec Googling for this ... This is the "freedesktop.org" specification ? Is there particular sub-spec I should look at ? > classifies icons by size (12x12, 16x16, 32x32, 36x36, etc...); > there can be multiple versions of a single icon at different sizes. > I find it more useful to classify them by "context", i.e., > icons for menus, for buttons, for toolbars, for dialog boxes, etc., ... > (This fits in nicely with Oakley's "Actions"). Hm. Not sure if I understand this correctly ... different icons for the same action but in different contexts ? > I've also found it useful to have variants based on state; Right ... Did not think of that, should have, we have stuff like that in the Tcl Dev Kit applications. although not everywhere I believe, there may parts managing it automatically ... > for instance > a toolbar icon might have a grayscale variant for when it's disabled > and a brighter variant for when it's active. (AIUI, Qt and Gtk+ > manage this programmatically. Tk can do this to a certain degree -- > autostippling images when disabled, f'rinstance This is something the package could handle internally ... Look for state specific icons first, and auto-stipple/brighten if no physical icon is found for the requested variant ... Question is, should we ? > -- but the results > aren't ideal.) Andreas. |