From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] 5/5 Graphical menu (gfxmenu)
Date: Sat, 21 Mar 2009 22:13:35 +0200 [thread overview]
Message-ID: <49C54A6F.1020503@nic.fi> (raw)
In-Reply-To: <20090131125939.0a5c3bce@gibibit.com>
Colin D Bennett wrote:
> This long-awaited patch adds graphical menu support to GRUB 2. It is
> largely the result of my work during the Google Summer of Code 2008.
>
> The graphical menu system supports image-based themes, of which I have
> created several sample themes[1].
>
> There are still a few important things that need to be done on gfxmenu
> before it is completely ready for end-users (off the top of my head):
>
> - Need a good way to switch themes at runtime. I want to add a popup
> menu that lists the available themes and lets the user choose one.
> (Currently the keys 1, 2, 3, and 4 are hardcoded to switch between my
> sample themes...)
Switching themes on runtime is not a priority. It is a nice to have
feature thou... but we can wait a bit with that.
> - gfxmenu interacts badly with gfxterm. Running commands from the
> terminal withing gfxmenu that switch the video mode
> ('videotest basic', for instance) cause a crash when the command
> returns. I think this has something to do with the interaction of
> video mode-switching and the GRUB output terminal.
I think we can live with some oddities so I would propose that we get
some version in. In fact it will make fixing bugs a bit more robust as
others can also contribute...
So whats the status of your actions. I think some of the patches were
already approved with some minor changes...
prev parent reply other threads:[~2009-03-21 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 20:59 [PATCH] 5/5 Graphical menu (gfxmenu) Colin D Bennett
2009-01-31 21:39 ` Vesa Jääskeläinen
2009-02-08 0:54 ` Robert Millan
2009-03-21 20:13 ` Vesa Jääskeläinen [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=49C54A6F.1020503@nic.fi \
--to=chaac@nic.fi \
--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.