All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GSoC Idea - Fancy Menu
Date: Thu, 27 Mar 2008 15:51:08 +0000	[thread overview]
Message-ID: <47EBC26C.4070702@ufomechanic.net> (raw)
In-Reply-To: <47EAAE07.10506@nic.fi>

* Vesa Jääskeläinen wrote, On 26/03/08 20:11:
> gopi wrote:
>> Hi!
>>
>> I'm GSoC student keen on taking up the "GRUB - Fancy Menu Inter face".
> Hi Gopi,
>
> If project is listed on that page then it means that feature is not
> yet completed and it would be good to have. Previous years we have
> only had opportunity to have only one student (I think) per year so
> far for GRUB project so to pick only one, compromises has to be made.
>
> You are free to address any questions on this mailing list about any
> GRUB related GSoC questions. If you want to know something about any
> of those entries, please address it with specific question.
>
> About Fancy Menu, there has been several emails in this mailing list
> and then there is also some info about it in our wiki:
>
> http://grub.enbug.org/Subprojects/GraphicalMenu
> http://grub.enbug.org/FancyMenu

As well as supporting fancy enhancements, the menu definitions ought
also to support simple menus.
I've worked with an serial port based LCD interface supplier to have the
standard LCD produced be suitable for grub menus.

Its a 4 key 2 line 16 character interface, with 8 programable characters
(like most LCD controllers).
It can be controlled via a standard serial interface.

So grub menus ought to support short labels as well as long titles and
graphical items; and so forth.

I merely mention this here so as to influence the data structures and
config items so that the fancy menus can be based on a widely usable
structure.

Sam




      reply	other threads:[~2008-03-27 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 23:12 GSoC Idea - Fancy Menu gopi
2008-03-26 20:11 ` Vesa Jääskeläinen
2008-03-27 15:51   ` Amin Azez [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=47EBC26C.4070702@ufomechanic.net \
    --to=azez@ufomechanic.net \
    --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.