unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: suggestions on toolbar icons
Date: Thu, 17 Mar 2005 18:08:01 +0100	[thread overview]
Message-ID: <00f101c52b14$94d4c700$0200a8c0@sedrcw11488> (raw)
In-Reply-To: b6d71523c7ddaeb3c711e3b1103d4a9a@swipnet.se

----- Original Message ----- 
From: "Jan D." <jan.h.d@swipnet.se>

> The tool bar icons follow the Gnome stock items
> (http://www.gtk.org/api/2.6/gtk/gtk-Stock-Items.html).  I think Emacs
> should follow them as close as it can, but we can of course change if
> there is a good reason.

Thanks for this pointer.


> >  - Arrows Previous, Next, Up, History Back, and History Forward:
> >    The structural-move icons (Previous, Next, Up) look too much
> >    like the chronological-move icons of Web browsers. I don't
> >    have a slam-dunk suggestion here, but we should come up with
> >    something better: browser users are used to these fat arrows
> >    for chronological moves. (It's best to avoid them altogether.)
>
> Gnome stock left/right/up.

I can actually not find that on the page above. That is I can find
GTK_STOCK_GO_UP, but there is as far as I can see nothing like
GTK_STOCK_GO_PREVIOUS (or LEFT). It seems like they forgot to distinguish
between GTK_STOCK_GO_BACK (ie a chronological move) and ...PREVIOUS (ie a
structural move).

I think this is pretty bad if you need both. On the page above they have
actually used filled arrows for structural moves (see the top). Is that
consistent with their suggestions?

I think we should distinguish between structural and cronological moves. As
I said in another message perhaps we do not need the structural moves in the
toolbar since they are in the text.

  reply	other threads:[~2005-03-17 17:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  1:27 suggestions on toolbar icons Drew Adams
2005-03-17  6:45 ` Lennart Borgman
2005-03-17  7:11 ` Jan D.
2005-03-17 17:08   ` Lennart Borgman [this message]
2005-03-17 20:06     ` Jan D.
2005-03-17 20:22       ` Lennart Borgman
2005-03-17 21:08         ` Jan D.
2005-03-17 18:33   ` Drew Adams
2005-03-17 19:41     ` Jan D.
2005-03-17 22:47       ` Drew Adams
2005-03-18  5:52         ` Jan D.
2005-03-18  7:36           ` David Kastrup
2005-03-18 17:37             ` Jan D.
2005-03-18 18:03               ` David Kastrup
2005-03-18 17:16           ` Drew Adams
2005-03-18 17:49             ` Jan D.
2005-03-17 21:44     ` David Kastrup
2005-03-18  1:40     ` Miles Bader
2005-03-18 17:16       ` Drew Adams
2005-03-18 17:56         ` David Kastrup
2005-03-18 18:20     ` Richard Stallman

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='00f101c52b14$94d4c700$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    --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).