#2842 NORM Trial-3: Need API for specifying custom icon states
Zarro Boogs per Child
bugtracker at laptop.org
Tue Aug 21 14:59:59 EDT 2007
#2842: Need API for specifying custom icon states
--------------------------+-------------------------------------------------
Reporter: Eben | Owner: dcbw
Type: enhancement | Status: new
Priority: normal | Milestone: Trial-3
Component: sugar | Version:
Resolution: | Keywords:
Verified: 0 |
--------------------------+-------------------------------------------------
Changes (by Eben):
* cc: benzea (added)
Comment:
Replying to [comment:1 marco]:
> * Try to fetch the pressed and insensitive icons from the icon theme
(whatever mechanism we use to expose it in the icon theme).
This makes sense. I think we agreed to append -pressed and -insensitive
to the standard naming scheme...
> * If that fails it should use the normal icon for the pressed state.
For the insensitive state, it should try to replace the stroke/fill
entities with insensitive colors (Eben can you remind me which colors we
should use?)
'''Pressed:''' We want to use the normal icon, and have the gray rounded
rect appear behind it on-press/when-selected anytime the pressed state is
not overridden. When is ''is'' overridden, we want to use the specified
icon and ''not'' use the rounded gray rect at all.
'''Insensetive:''' We want to employ some automatic "graying-out" of the
basic icon when no icon is specified for the insensitive state. The rule
that's easy to apply is to use the alpha channel for the default icon and
place it on a solid button-gray fill, so the entire icon is one color --
middle gray. That's the simplest, though it may be better to actually do
a strong reduction of contrast and then shift the values so that it's
centered on middle-gray, but not entirely one color. (I discussed these
options with benzea) Anyway, we want to use this automatic approach only
when a custom icon isn't specified; otherwise we just use the custom
insensitive icon itself.
This might have been just what you meant Marco, but I wanted to highlight
the fact that the "default" behaviors for both states should only occur
when not overridden.
--
Ticket URL: <http://dev.laptop.org/ticket/2842#comment:2>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list