Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II - DVB

[Trent Piepho <xyzzy@speakeasy.org>]

On Fri, 4 May 2007, Roman Zippel wrote:
> I don't quite understand. With the menuconfig changes more menu entries
> should  appear on the left side, so I don't understand why you have to
> "drill down" to reach it.
> The rule for menu to appear on the left side is relatively simple - all
> its parents must be of menu type as well. So if a menuconfig is on the
> right side it must have a normal config entry as parent.

I think that's it.  The media tree was done with options to select the core
system module, then a menuconfig that depended on that which the drivers
were under.

> > > menuconfig XXXX
> > > if XXXX
> > > [....all the other options....]
> > > endif
> > >
> > > Into this:
> > >
> > > menuconfig XXXX
> > > [....all the other options....]
> > > endmenu
> > >
> > > The reason is that a frontend would easily be able to understand the coupling
> > > between the "menuconfig XXXX" and the "if XXXX".  It will make it easier for
> > > the frontend to see that all the options are inside and controlled by the
> > > enclosing menuconfig.
>
> If the frontend wants to change the behaviour of a menuconfig, it can
> already do that, so this doesn't require a syntax change.

How about these examples:

menuconfig FOO
if FOO
config A
	depends on FOO
endif
config B
if FOO
config C
	depends on FOO
endif

Or this:
menu FOO
menuconfig BAR
config A
menuconfig BAZ
config B
endmenu

How does it show the first one, keeping the config entries in the correct
order and put them into the menu at the same time?

And which of what should the second be show?

foo
\-bar
  \-baz

or

foo
|-bar
\-baz

There is no question with menus, as the menu tree is clearly lexically
defined by the matching menu / endmenu pairs.  But menuconfig doesn't work
that way, and it seems like it would make more sense if it did.