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 21:25:50 +0200	[thread overview]
Message-ID: <4732113E.5070305@nic.fi> (raw)
In-Reply-To: <fgt213$ts$1@ger.gmane.org>

Markus Elfring wrote:
>> And what is wrong with current config file?
>> http://grub.enbug.org/grub.cfg
> 
> How much documentation is available for this domain-specific language?
> Does a grammar exist for the data format?

Marco Gerards has been working on the grub scripting language. So he
might be able to give some insights in case Wiki does not feature enough
information.

> http://grub.enbug.org/Subprojects/GraphicalMenu
> 
> I imagine that additional attributes will be needed.
> - Identifier: optional alphanumeric key
> - Parent: index number or menu identifier

Menu commands can have children already so you would get hierarchy
information from there. Shortcut key you could just add as extra
argument for menu, like --hotkey="1"

In example:

menu "foo" {
  menu "bar" {
    menu "zot" {
    }
  }
}

Though I am not sure how well this outline view is supported by the
current parser. Marco, perhaps you could share some insights?

> I hope that it can be avoided to reinvent a wheel. How much features would you
> like to copy from OML or OPML?

I had a look at example mp3 playlist in opml format and it seems to be
data description language (like what xml is). What we have in grub
script is a scripting language that has commands to construct data (menu).

>> 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
> 
> How much will a browser depend on an operating system?

In case you mean graphical menu, then it does not depend on any
operating system. GRUB is standalone application that executes on system
context.

> How near will a boot environment come to OS functionality?

That I leave unanswered.




  reply	other threads:[~2007-11-07 19:28 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
2007-11-07 19:00           ` Markus Elfring
2007-11-07 19:25             ` Vesa Jääskeläinen [this message]
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=4732113E.5070305@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.