From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: menu loop (patch)
Date: Sat, 19 Jul 2008 17:40:43 +0200 [thread overview]
Message-ID: <20080719154043.GG23778@thorin> (raw)
In-Reply-To: <20080717212227.GA11725@pina.cat>
On Thu, Jul 17, 2008 at 11:22:27PM +0200, Carles Pina i Estany wrote:
>
> Hello,
Carles! Que n'és de petit el món ;-)
> I'm a Grub user (thanks for your nice work!) and I always wanted to have
> a menu that "loops". Like, if you press down and you are in the last
> option it goes to the first one, and if you press up but you are int he
> first option goes to the last.
>
> Attached comes a patch against revision 1718.
>
> Of course, feel free to comment anything about it. I'm open to change,
> fix, etc.
>
> I also don't know if this functionality is not in Grub because you
> thought that was better to not have this functionality.
>
> I've copied/change a few lines (after the patch, lines 425-428 are the
> same than lines 347-350). I don't think that it's needed to refactor but
> if you think so I can do it.
I'm not sure if this is intentional. Size is not important in this part of
the code, but in other UI menus (e.g. Iceweasel or GNOME) I notice this is
not done. It could also be a nuissance for users who want to go rapidly to
the top or bottom (sure, they can use PgUp/PgDn, but then aren't we making
the behaviour of those keys inconsistent with arrows?).
Also, if you (or anyone) can point to a "usability best practices" reference
saying this has been carefuly analized and one of the options was found to be
better, I think this would help us make a decision.
What does everyone else think?
Colin, does this affect your graphical menu work in some way? I suppose the
same situation applies the same way to the upcoming new menu. Or perhaps
this can be made more flexible and be toggled by some CSS magic?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-07-19 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 21:22 menu loop (patch) Carles Pina i Estany
2008-07-19 15:40 ` Robert Millan [this message]
2008-07-19 17:21 ` Carles Pina i Estany
2008-07-19 19:52 ` Robert Millan
2008-07-19 22:12 ` Carles Pina i Estany
2008-07-19 23:26 ` Isaac Dupree
2008-07-19 23:31 ` Carles Pina i Estany
2008-07-19 23:45 ` Isaac Dupree
2008-07-20 4:24 ` Colin D Bennett
2008-07-19 17:34 ` Colin D Bennett
2008-07-19 19:58 ` Robert Millan
2008-07-19 20:31 ` Yoshinori K. Okuji
2008-07-19 22:06 ` Carles Pina i Estany
2008-07-19 22:15 ` Robert Millan
2008-07-19 22:28 ` Colin D Bennett
-- strict thread matches above, loose matches on Subject: below --
2008-07-20 6:21 chaac
2008-07-20 8:49 ` Carles Pina i Estany
2008-07-22 21:40 ` Robert Millan
2008-08-05 7:15 ` Vesa Jääskeläinen
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=20080719154043.GG23778@thorin \
--to=rmh@aybabtu.com \
--cc=grub-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.
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.