Re: [PATCH] Use new tango icon for bluez gnome

Marcel Holtmann <[email protected]>
Newsgroups gmane.linux.bluez.devel
Message-ID <1202661736.7664.91.camel@violet>
Hi Jaap,

> > > Andreas Nilson has made new tango icons for bluez-gnome. (The
> > > stock_bluetooth icon will be removed from gnome-icon-theme, because
> > > it's deprecated)
> >
> > do icons really should belong in the package itself. I was under the
> > impression that it is better to have them in a common package and the
> > applications are going to reference them only. I am happy to follow the
> > GNOME policy here, but someone has to tell me what is the current way to
> > go for these.
> 
> The GNOME policy is that only the icons of the icon naming
> specification [1] will be in gnome icon theme. Apps have to ship there
> own icons.

why don't we make the Bluetooth icons then part of the icon naming
specification?

> > If we are re-working the icon anyway, then I like to request a grayed
> > out icon (for disabled or inactive adapters) and one that indicates an
> > active state. For example with yellow instead of white for the bind
> > rune.
> >
> Shall we start with applying this patch? It makes bluez-gnome blend in
> better with current desktops and we don't depend on gnome-icon-theme
> anymore. There is already a request to remove the stock_bluetooth icon
> [2]
> 
> I'll ask Andreas if he can cook up bluetooth-enabled and
> bluetooth-disabled icons

I would like to do it all in one run. Since we depend now on the
notifications, we can actually better use the blinking capability and
create better visibility for the end user.

Ask Andreas how long it would take. I am not an graphics guy at all. So
I would have no clue.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.