All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] Multi-terminal support (Re: [PATCH] terminal split)
Date: Sat, 22 Nov 2008 20:54:57 +0100	[thread overview]
Message-ID: <20081122195457.GA7779@thorin> (raw)
In-Reply-To: <200811221842.54928.okuji@enbug.org>

On Sat, Nov 22, 2008 at 06:42:54PM +0100, Yoshinori K. Okuji wrote:
> 
> However, whenever you want to do more than that, you must control each 
> terminal differently. In particular, the menu code. The menu interface may 
> not be uniform with all terminals. A terminal might have the size 80x25. 
> Another might have 120x40. This is more complex with graphical terminals.

This problem does only happen with output terminals, right?  My primary
concern are input terminals, because if we want to support USB keyboards
we need to probe from both USB and AT ones at the same time.

> I like the idea that GRUB displays the user interface simultaneously. But this 
> requires a lot of refactoring. Probably, the menu code will have to iterate 
> all terminals explicitly, and make actions differently for each terminal, 
> based on the capabilities. With the menu editor, how should the cursor be 
> managed? We need to think a lot.

I've been thinking... what if we make this generic?  I.e. with an event loop,
then terminals can register their poll functions to it, and write their stuff
to a shared resource the rest of GRUB can read from.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2008-11-22 19:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 18:11 [PATCH] terminal split Robert Millan
2008-11-04 15:52 ` Yoshinori K. Okuji
2008-11-04 17:14   ` Robert Millan
2008-11-06 17:05     ` Yoshinori K. Okuji
2008-11-07 19:13       ` Robert Millan
2008-11-04 18:31   ` Vesa Jääskeläinen
2008-11-06 17:20     ` Yoshinori K. Okuji
2008-11-07 19:07       ` Robert Millan
2008-11-09  7:22         ` Yoshinori K. Okuji
2008-11-04 18:53 ` Vesa Jääskeläinen
2008-11-04 19:12   ` Robert Millan
2008-11-04 19:49     ` Colin D Bennett
2008-11-07 19:26     ` [RFC] Multi-terminal support (Re: [PATCH] terminal split) Robert Millan
2008-11-22 17:42       ` Yoshinori K. Okuji
2008-11-22 19:54         ` Robert Millan [this message]
2008-11-25 21:23           ` Yoshinori K. Okuji
2008-11-26 11:41             ` SPAM-LOW: " Amin Azez
2008-11-28 20:38             ` Robert Millan
2008-11-29 21:20               ` 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=20081122195457.GA7779@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.