unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: Drew Adams <drew.adams@oracle.com>, Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: suggestions on toolbar icons
Date: Thu, 17 Mar 2005 21:06:43 +0100	[thread overview]
Message-ID: <7c0c2abc2e70701983a11d21130ca822@swipnet.se> (raw)
In-Reply-To: <00f101c52b14$94d4c700$0200a8c0@sedrcw11488>

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

>> 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).

No, previous and next are missing.  As is open directory.  I guess they 
make stock items for the most common operations, previus/next/open 
directory does not seem to be among them.

>
> 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?

They really don't say mush on the issue, the guidelines are at 
http://developer.gnome.org/projects/gup/hig/2.0/.  Some applications, 
like gthumb, uses a filled arrow that points into a "file"-like 
background, see attachement.


[-- Attachment #2: prev.jpg --]
[-- Type: image/jpeg, Size: 1094 bytes --]

[-- Attachment #3: Type: text/plain, Size: 12 bytes --]



	Jan D.



[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2005-03-17 20:06 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
2005-03-17 20:06     ` Jan D. [this message]
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=7c0c2abc2e70701983a11d21130ca822@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=drew.adams@oracle.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).