From: Marcel Holtmann <marcel@holtmann.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 18:52:46 +0100 [thread overview]
Message-ID: <1202665966.7664.97.camel@violet> (raw)
In-Reply-To: <8a8adccc0802100924m58527440rcd3d6ffb062c742@mail.gmail.com>
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?
> >
>
> I agree with you that it makes sense, but Rodney Dawes the icon naming
> spec and gnome icon theme maintainer thinks it doesn't make sense. See
> http://bugzilla.gnome.org/show_bug.cgi?id=505116
> I've tried to convince him several times of including some icons, but
> he's very keen on keeping the icon set as minimal as possible. You can
> try if you want.
I don't even bother. Eventually they change their mind back and I am not
getting in their way. I couldn't care less.
> > 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.
> >
>
> You could do me a favor by applying the patch. Now and then I have to
> feel that the time I put in patches is appreciated.
>
> Patches have the tendency not to apply cleanly anymore after a while
> and thus lead to more work.
>
> Even with your suggested enhancements (having enabled/disabled icons)
> this patch still applies. If you manage to convince Rodney to get the
> icons in gnome-icon-theme I'll send you the necessary patch.
I did my own patch to handle the update-icon-cache thing properly in
cases of distcheck and the maintainers.
For now I also only included the 22x22 icons. Still have to re-think the
file structure. Would be nice if we had some nice templates for doing
this properly within one directory.
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/
_______________________________________________
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 17:52 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
2008-02-10 16:42 ` Marcel Holtmann
2008-02-10 17:24 ` Jaap A. Haitsma
2008-02-10 17:52 ` Marcel Holtmann [this message]
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=1202665966.7664.97.camel@violet \
--to=marcel@holtmann.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