From: David Kastrup <dak@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: Item for TODO?
Date: Sun, 23 Jan 2005 11:53:58 +0100 [thread overview]
Message-ID: <x5sm4s1kmx.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1CsV5d-00052D-OR@fencepost.gnu.org> (Richard Stallman's message of "Sat, 22 Jan 2005 18:54:49 -0500")
Richard Stallman <rms@gnu.org> writes:
> I can configure a menu-item as a button in X, but if I do the
> same on a tty it just presents me with a list of completions (of
> top-level menu items). ... Thats not true. Text-only does not
> mean "no mouse". The command tmm-menubar-mouse can be invoked by
> clicking on on the menubar with the mouse.
>
> If mouse selection doesn't work right for a menu bar item that has
> no menu, then it's a bug. Fixing it should be much easier than
> adding a separate tool bar. Also, since it is a bug fix, it is ok
> to do it now.
>
> I still don't think that a tool bar would have any advantage over
> the menu bar, for a tty.
The difference between a toolbar and a menu is that the toolbar
contains immediate actions, only the most important ones. The screen
real estate on a tty is limited: our current implementation of
keyboard menus is not really convenient for use with a mouse, but can
be configured to take away no space when not used. Implementing a
toolbar would at least require short button names: I don't think that
we have them available in general. Maybe one would need mouse-over
action that changes a button [Pre] to [Preview] or similar.
mouse-over action would also make possible having a menu just appear
when the mouse cursor is in the top tty row.
Anyway, there are a number of things that might be worth thinking
about, in particular in connection with mouse-over (and don't forget
that at the time frames we are talking of, we also might negotiate
mouse-over events with gpm and xterm people).
But that discussion is something for after the release, at best. I
think it would take even too much time to agree on something
definitive for the TODO file.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2005-01-23 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 5:58 Item for TODO? Nick Roberts
2005-01-21 15:55 ` Stefan Monnier
2005-01-21 16:42 ` John Paul Wallington
2005-01-22 8:36 ` Eli Zaretskii
2005-01-22 11:09 ` Nick Roberts
2005-01-22 11:52 ` Eli Zaretskii
2005-01-22 12:25 ` David Kastrup
2005-01-22 2:52 ` Richard Stallman
2005-01-22 7:42 ` Nick Roberts
2005-01-22 23:54 ` Richard Stallman
2005-01-23 0:35 ` Nick Roberts
2005-01-24 6:50 ` Richard Stallman
2005-01-23 10:53 ` David Kastrup [this message]
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=x5sm4s1kmx.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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).