From: "Jaap A. Haitsma" <jaap@haitsma.org>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Use new tango icon for bluez gnome
Date: Sun, 10 Feb 2008 17:31:43 +0100 [thread overview]
Message-ID: <8a8adccc0802100831k107d6d0akc0cfe388b61b7810@mail.gmail.com> (raw)
In-Reply-To: <1202659315.7664.88.camel@violet>
On Feb 10, 2008 5:01 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> 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.
> 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
Jaap
[1] http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
[2] http://bugzilla.gnome.org/show_bug.cgi?id=505116
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-10 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 15:01 [Bluez-devel] [PATCH] Use new tango icon for bluez gnome Jaap A. Haitsma
2008-02-10 16:01 ` Marcel Holtmann
2008-02-10 16:31 ` Jaap A. Haitsma [this message]
2008-02-10 16:42 ` Marcel Holtmann
2008-02-10 17:24 ` Jaap A. Haitsma
2008-02-10 17:52 ` Marcel Holtmann
2008-02-10 18:10 ` Jaap A. Haitsma
2008-02-10 20:08 ` Marcel Holtmann
2008-02-10 18:21 ` Jaap A. Haitsma
2008-02-10 20:09 ` Marcel Holtmann
2008-02-10 21:54 ` Jaap A. Haitsma
2008-02-10 22:12 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a8adccc0802100831k107d6d0akc0cfe388b61b7810@mail.gmail.com \
--to=jaap@haitsma.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox