unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: suggestions on toolbar icons
Date: Thu, 17 Mar 2005 22:44:23 +0100	[thread overview]
Message-ID: <x5r7ie6j7s.fsf@lola.goethe.zz> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICOEEECFAA.drew.adams@oracle.com> (Drew Adams's message of "Thu, 17 Mar 2005 10:33:59 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

[...]

>     The point of stock items is that themes may change them and
>     applications that uses stock items change appearence
>     automatically.
>
> I think that Emacs could do better than what is there now,

I agree with that assessment, but I think the best way to change this
is to tell the GNOME artists.

> but I do respect that general argument. I wasn't aware of this.
>
>     Gnome is the GNU desktop environment, so aligning Emacs with Gnome
>     where possible makes sense. It does not make sense to me to change
>     Emacs for the benefit of any other platform.
>
> This is not about "any other platform". Aligning Emacs with GNOME is
> fine, in principle. Recognize, however, that it can also mean a
> straightjacket at times - Emacs will not be _better_ than whatever
> GNOME has already defined.

Then GNOME should become better.  There is no sense in splitting
efforts here.  If an icon is unclear in meaning, we should report it
to the GNOME artists instead of creating some half-baked inconsistent
icon ourselves.  They have the means to create stuff that matches
their style better than what we could come up with.  If they made
unfortunate choices at times, there is no reason not to tell them.

> Sorry, I'm not an artist or an image guru. I think my descriptions
> got the point across. It's a moot point anyway, if we are to adhere
> to the GNOME "standard".

Or the GNOME standard to its users' needs.  Really, there is no need
to be fatalistic about it.  Make a proposal and send it to the GNOME
lists.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2005-03-17 21:44 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.
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 [this message]
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=x5r7ie6j7s.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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).