From: Bill Wohler <wohler@newt.com>
Cc: emacs-devel@gnu.org
Subject: Re: Icon update
Date: Fri, 31 Mar 2006 09:37:35 -0800 [thread overview]
Message-ID: <10546.1143826655@olgas.newt.com> (raw)
In-Reply-To: <442D1EEE.1000705@swipnet.se>
Jan D. <jan.h.d@swipnet.se> wrote:
> Bill Wohler wrote:
> > "Jan D." <jan.h.d@swipnet.se> writes:
> >
> >>I've attached some screenshots of these situations. I think before we
> >>release this we need to find stock items for everything. In Info mode
> >>there are also icons that don't have any stock definition, so arrows
> >>may look differently.
> > Since you're more familiar with GTK, can you please suggest a
> > specific
> > proposal?
> > While updating the icons I was thinking of stock_previous,
> > stock_next,
> > and stock_up (from GNOME) to replace prev_node, next_node, and up_node
> > respectively but wasn't sure how folks would respond to that.
>
> Can you link to them?
I'm not sure I know what you mean by that.
> > This means that all calls to tool-bar-* in all modes to need to be
> > updated. It would be good to avoid this. Plus, this approach doesn't
> > scale to other systems.
> > I think it would be preferable to keep the tool-bar-* calls the way
> > they are and provide a table of Emacs icon names to the icon name for
> > the system being used. That way, Emacs will honor the user's theme
> > whether it is being run under GNOME, KDE, or Windows, without
> > requiring code changes from all Emacs package developers.
> >
>
> But that means that the old way of changing icons (copying a new file
> to where Emacs looks for icons) does not work.
Hmmm, you're right. I see two approaches.
1. Devise a scheme that provides the following icon priorities:
a. Personal icons
b. Theme icons
c. Emacs built-in icons
2. Use the theme as I had proposed. The user personalizes the icon not
by adding their icons to image-load-path, but rather by adding their
icons to the GNOME theme. We document this.
I suspect that the latter is more germane to a GNOME user.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
next prev parent reply other threads:[~2006-03-31 17:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 22:57 Icon update Bill Wohler
2006-03-26 22:59 ` Bill Wohler
2006-03-27 19:55 ` David Kastrup
2006-03-28 6:33 ` Jan D.
2006-03-29 0:42 ` Leon
2006-03-29 4:17 ` Bill Wohler
2006-03-29 10:11 ` Jan D.
2006-03-29 19:03 ` Leon
2006-03-29 20:06 ` Leon
2006-03-29 20:34 ` Stefan Monnier
2006-03-29 20:42 ` Leon
2006-03-30 7:05 ` Jan D.
2006-03-30 19:39 ` Bill Wohler
2006-03-31 12:22 ` Jan D.
2006-03-31 17:37 ` Bill Wohler [this message]
2006-04-01 12:19 ` Jan D.
2006-04-01 16:22 ` Bill Wohler
2006-04-01 20:06 ` Bill Wohler
2006-04-03 6:28 ` Jan D.
2006-04-03 22:09 ` Bill Wohler
2006-04-04 6:48 ` Jan D.
2006-04-04 19:04 ` Bill Wohler
2006-04-04 19:09 ` Lennart Borgman
2006-04-04 19:30 ` Bill Wohler
2006-04-05 7:08 ` Jan D.
2006-04-05 7:13 ` Miles Bader
2006-03-30 20:41 ` Leon
2006-03-31 1:52 ` Bill Wohler
2006-03-31 12:29 ` Jan D.
2006-03-29 21:47 ` Bill Wohler
2006-03-29 22:50 ` Stefan Monnier
2006-03-30 6:56 ` Jan D.
2006-03-30 20:26 ` Leon
2006-03-30 6:43 ` Jan D.
2006-03-28 19:22 ` Bill Wohler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10546.1143826655@olgas.newt.com \
--to=wohler@newt.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).