All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: grub-devel@gnu.org
Subject: Re: gfxmenu status? [was: Serial and graphical console at the same time]
Date: Fri, 26 Feb 2010 12:46:02 -0800	[thread overview]
Message-ID: <20100226124602.50f846ec@svelte> (raw)
In-Reply-To: <a5d587fb1002180550n2b1a05c2ja5e32174c97a3f77@mail.gmail.com>

On Thu, 18 Feb 2010 14:50:15 +0100
Michal Suchanek <hramrach@centrum.cz> wrote:

> On 18 February 2010 01:48, Colin Watson <cjwatson@ubuntu.com> wrote:
> > On Wed, Feb 17, 2010 at 05:37:16PM -0700, Joey Korkames wrote:
> >> Christian Auby writes:
> >>> How would I go about setting up grub2 with both serial console and
> >>> graphical console?
> >>
> >> You can't run simultaneous consoles with a stock grub2 build.
> >> The experimental branch does support it though:
> >> http://robertmh.wordpress.com/2009/12/25/multiple-grub-terminals/#comment-520
> >
> > The relevant code was merged into trunk on 2010-01-09.
> >
> 
> How does the gfxmenu work in this case?
> 
> And how does it work in the simpler cases, anyway?
> 
> Is there some documentation or at least samples?
> 
> Everywhere it's said the menu is MVC based. I am not expert on MVC but
> I don't see anything remotely reminiscent of MV separation, the wiki
> pages describe just a UI toolkit without most of the MVC parts.

I think that only the menu/menuitems are the model, but there are two
views on the menu model: (1) the text-mode menu and (2) the graphical
menu.  The GUI component model is fairly limited at this point but
there's no reason it couldn't be expanded to a wider variety of widgets
that might support MVC (for instance a text area that uses a model
separate from its view).

Regards,
Colin



      reply	other threads:[~2010-02-26 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 13:50 gfxmenu status? [was: Serial and graphical console at the same time] Michal Suchanek
2010-02-26 20:46 ` Colin D Bennett [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100226124602.50f846ec@svelte \
    --to=colin@gibibit.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.