From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>
Cc: 3022@emacsbugs.donarmstrong.com
Subject: bug#3022: 23.0.92; triangle images in Customize buffers are just plain bad
Date: Sat, 31 Oct 2009 09:09:50 -0700 [thread overview]
Message-ID: <83CEEFF8DC7149C1A89D91B6DD5BF312@us.oracle.com> (raw)
In-Reply-To: <877hub38qf.fsf@stupidchicken.com>
> > While the idea behind the triangles (arrows) in Customize is good
> > (actually, I believe it was I who suggested it), the
> > current effect is quite bad.
> >
> > If the value is shown, then the triangle points downward. Typically,
> > that symbol means that clicking it will display something additional
> > below the symbol. Instead, the value disappears.
> >
> > If the value is not shown, the the symbol is a right-pointing
> > triangle. That's OK in this case, since it suggests that clicking it
> > will display something to the right, and the value is to the right.
> >
> > However, for the symbol that replaces `More', a right-pointing
> > triangle is inappropriate, since the text is not displayed to its
> > right, but below it.
>
> This is a very standard user interface idiom, known as "disclosure
> triangles".
Calling it by name and "very standard" doesn't improve anything. It was I who
suggested the idea in the first place. The idea is fine, as I said already.
"The current _effect_ is bad." That's the point: it is simply not done right.
The result is confusion and easily missing information. See above for details.
Doors on buildings (known as "doors") are a very standard architecture idiom.
But some doors are poorly designed.
next prev parent reply other threads:[~2009-10-31 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 15:04 bug#3022: 23.0.92; triangle images in Customize buffers are just plain bad Chong Yidong
2009-10-31 16:09 ` Drew Adams [this message]
2009-11-06 1:50 ` Juri Linkov
2009-11-06 2:53 ` Lennart Borgman
2012-02-22 2:28 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2009-04-16 20:37 Drew Adams
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=83CEEFF8DC7149C1A89D91B6DD5BF312@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3022@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.