Markus Elfring <[EMAIL PROTECTED]> writes:
>> I want to make something to generate menu entries from a script.
>> Is that what you mean?
>
> I see two places where common settings could be written.
> 1. menu configuration
> 2. source code generation script
>
> Where do you want to place them?
Bot
Markus Elfring <[EMAIL PROTECTED]> writes:
>> Personally I first want to focus on getting what we have to work,
>> before even thinking about anything else. Ideas are good, but having
>> *something* to use is better :-)
>
> It seems that all relevant design aspects are not clear at the moment.
>
> I want to make something to generate menu entries from a script.
> Is that what you mean?
I see two places where common settings could be written.
1. menu configuration
2. source code generation script
Where do you want to place them?
Regards,
Markus
> Personally I first want to focus on getting what we have to work,
> before even thinking about anything else. Ideas are good, but having
> *something* to use is better :-)
It seems that all relevant design aspects are not clear at the moment.
I would prefer a bit more clarity about the open iss
Markus Elfring <[EMAIL PROTECTED]> writes:
>> 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"
>
> Will an explanation of the data format be added to the wiki?
>
>
>> In ex
Vesa Jääskeläinen <[EMAIL PROTECTED]> writes:
> 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
Markus Elfring wrote:
>> 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"
>
> Will an explanation of the data format be added to the wiki?
I assume someone will at some po
> 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"
Will an explanation of the data format be added to the wiki?
> In example:
> menu "foo" {
> menu "bar" {
> menu "zo
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
> 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?
http://grub.enbug.org/Subprojects/GraphicalMenu
I imagine that additional attributes will be needed.
- Id
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 flexibl
* Vesa Jääskeläinen wrote, On 06/11/07 21:37:
> Amin Azez wrote:
>
>>
>> At the same time, can we consider supporting specification of
>> alternative short menu texts, suitable for display on 16 character LCD
>> screens.
>>
>> I'll be doing some work on grub-legacy to support boot menu's on such
> 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 whi
Amin Azez wrote:
> * Markus Elfring wrote, On 05/11/07 22:01:
>>> And then add something like:
>>> set menumode=outline
>>> set menumode=hierarchical (or normal, default)
>>>
>>
>> Can a data format like it is specified by the outline markup language be
>> supported by the GRUB 2 boot loader?
Markus Elfring wrote:
>> And then add something like:
>> set menumode=outline
>> set menumode=hierarchical (or normal, default)
>
> Can a data format like it is specified by the outline markup language be
> supported by the GRUB 2 boot loader?
> http://en.wikipedia.org/wiki/OML
I do not fancy XML
* Markus Elfring wrote, On 05/11/07 22:01:
>> And then add something like:
>> set menumode=outline
>> set menumode=hierarchical (or normal, default)
>>
>
> Can a data format like it is specified by the outline markup language be
> supported by the GRUB 2 boot loader?
> http://en.wikipedia.org/
> And then add something like:
> set menumode=outline
> set menumode=hierarchical (or normal, default)
Can a data format like it is specified by the outline markup language be
supported by the GRUB 2 boot loader?
http://en.wikipedia.org/wiki/OML
Is an alternative specification needed in this cont
Markus Elfring wrote:
> I suggest to add the capability to present the menu as an outline.
> http://en.wikipedia.org/wiki/Outline#Sample_alphanumeric_outline
>
> Example boot menu:
> A) Windows:
> - XP
> - Vista
>
> B) Linux:
> - Knoppix
> - Debian
> * Etch
> - Red Hat
> * Fedora
> - openSUSE
Vesa asked for feedback on GUI design a while ago. CCing!
On Sat, Nov 03, 2007 at 08:20:22PM +0100, Markus Elfring wrote:
> Hello,
>
> I suggest to add the capability to present the menu as an outline.
> http://en.wikipedia.org/wiki/Outline#Sample_alphanumeric_outline
>
> Example boot menu:
>
Hello,
I suggest to add the capability to present the menu as an outline.
http://en.wikipedia.org/wiki/Outline#Sample_alphanumeric_outline
Example boot menu:
A) Windows:
- XP
- Vista
B) Linux:
- Knoppix
- Debian
* Etch
- Red Hat
* Fedora
- openSUSE
* 10.2 release
* 10.3 debug
- Ubuntu
20 matches
Mail list logo
