All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Outline menu
Date: Wed, 07 Nov 2007 17:44:44 +0200	[thread overview]
Message-ID: <4731DD6C.6080807@nic.fi> (raw)
In-Reply-To: <fgrqo0$p1s$1@ger.gmane.org>

Markus Elfring wrote:
>> I do not fancy XML for the boot loader... and I do not see a need to yet
>> another configuration file format for menus. We already have menu
>> command that can be used to build menus. Perhaps you can convince me
>> otherwise?
> 
> I imagine that GRUB can become so flexible that it can be specified which data
> formats should be parsed. If the target boot environment has not got enough
> resources for XML and XSLT processing, an customised configuration file format
> must be used to specify the required menu attributes. Do you know any other
> standard file format for outlines that might be more resource-friendly?

And what is wrong with current config file?

http://grub.enbug.org/grub.cfg

If you refer to layout, then CSS style file should be suitable. We don't
even need to support everything, just a custom subset so we can define
everything that is needed. Configuring layout style file would just be
another command or environment variable.

You can read my idea of visual layout from "Layout testing for graphical
menu" in mailing list archive:

http://lists.gnu.org/archive/html/grub-devel/2007-10/msg00103.html

Please explain your agenda so it is easier to discuss it. File format is
just a way to store information, nothing more. We are here talking about
functionality before making any final choices (which can be of course
replaced in future if there becomes more superior choice to choose from).




  reply	other threads:[~2007-11-07 15:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 19:20 Outline menu Markus Elfring
2007-11-05 15:38 ` Robert Millan
2007-11-05 15:56 ` Vesa Jääskeläinen
2007-11-05 22:01   ` Markus Elfring
2007-11-06 10:01     ` Amin Azez
2007-11-06 21:37       ` Vesa Jääskeläinen
2007-11-07 15:56         ` Amin Azez
2007-11-06 21:35     ` Vesa Jääskeläinen
2007-11-07  7:50       ` Markus Elfring
2007-11-07 15:44         ` Vesa Jääskeläinen [this message]
2007-11-07 19:00           ` Markus Elfring
2007-11-07 19:25             ` Vesa Jääskeläinen
2007-11-08  6:05               ` Markus Elfring
2007-11-08 16:23                 ` Vesa Jääskeläinen
2007-11-08 18:15                   ` menu attributes Markus Elfring
2007-11-08 18:55                     ` Vesa Jääskeläinen
2007-11-08 18:30                   ` Improvements for menu display Markus Elfring
2007-11-10 16:19                 ` Outline menu Marco Gerards
2007-11-11  8:20                   ` Markus Elfring
2007-11-18 11:07                     ` Marco Gerards
2007-11-10 16:17               ` Marco Gerards
2007-11-11  8:01                 ` Markus Elfring
2007-11-18 11:06                   ` Marco Gerards
2007-11-26 10:54                     ` software design clarification Markus Elfring

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=4731DD6C.6080807@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.