[syslinux] submenus and menu title

[Ady]

Date sent:      	Tue, 18 Sep 2012 18:19:48 -0400
From:           	Gene Cumm <gene.cumm at gmail.com>
To:             	For discussion of Syslinux and tftp-hpa 
<syslinux at zytor.com>
Subject:        	Re: [syslinux] submenus and menu title
Send reply to:  	For discussion of Syslinux and tftp-hpa 
<syslinux at zytor.com>
	<mailto:syslinux-request at zytor.com?subject=unsubscribe>
	<mailto:syslinux-request at zytor.com?subject=subscribe>

> On Sep 18, 2012 12:02 PM, "Ady Ady" <ady-sf at hotmail.com> wrote:
> > Hello hpa,
> > I'd like to know if you need more info / pointers other than that
> >  ( http://www.syslinux.org/archives/2012-September/018075.html ).
> > In addition, I'm already working on updated documentation about submenus for
> >  [vesa]menu.c32 to be added to the wiki (including my suggestions for
> >  improvements for "case#4" and "case#8"). Any suggestion about an adequate
> >  name for such new wiki page?
> > TIA,
> > Ady.
> 
> I'm planning on splitting doc/syslinux.txt to separate the config from
> installer portions.  I'd think the submenu stuff should still stay in
> doc/menu.txt but perhaps also include some clean examples.
> 
> 
> --Gene

Hello Gene,

I think that submenus involve many details that are not necessary for 
all users. Currently almost no information about submenus is 
documented, except the mention of the existence of a few directives.

In my case, it took me "too much" time to understand the "oddities" I 
was seeing. Even a developer as yourself, with experience in 
Syslinux, was unaware of some of those fallback rules we are 
covering.

To mention just some points to be documented, the potential 
restrictions for "tagname", or its equivalent use as "label", or 
examples for
 [MENU] INCLUDE filename.cfg [tagname] 
in addition to the sample cases I presented here in this thread, or 
even multiple levels of submenus, or using other alternatives 
methods. I think it's too much to add to menu.txt.

This is not the only matter that needs more documentation for the 
user (author of cfg files). IMHO, adding references (whether in text 
files as "read some_file.txt for more info about submenus", or in the 
wiki as internal links) generates a main (already "long") menu.txt 
that is easier to read and follow, specially for newcomers. A 
separate document would provide more info for those users 
specifically interested. The reader not interested in using submenus 
would continue reading the main document about the configuration of 
[vesa]menu.c32 with a more natural flow.

In any case, after 2 months of presenting here my request / 
suggestion, I have no indication whether it is going to be 
implemented some time in the foreseeable future, even after 
summarizing it in one email.

Please don't misunderstand me. I'm not complaining, at all. I just 
would rather have an indication that I'm not wasting my (and yours, 
and probably others') time with this issue.

I have already prepared a "media wiki table" with the fallback rules, 
and I can easily convert it to a text-only table for inclusion in a 
text file (to be displayed in some mono-space font, for better 
clarity). This is _almost_ independent of the improvements I am 
suggesting. If the improvements are implemented, I'll gladly test 
them again (not only with the 8 cases I presented here but also with 
all the others I have seen in live CDs, and whichever other case I 
can think about), so to present accurate and updated documentation 
and feedback.

I can help with documentation, but I cannot implement my suggestion 
by myself.

TIA,
Ady.