public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dirk Gouders <dirk@gouders.net>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [RFC] mconf: suppress empty submenus
Date: Fri, 17 May 2013 01:04:04 +0200	[thread overview]
Message-ID: <20130516230404.GB19534@free.fr> (raw)
In-Reply-To: <1368626738-31911-1-git-send-email-dirk@gouders.net>

Dirk, All,

On 2013-05-15 16:05 +0200, Dirk Gouders spake thusly:
> I noticed that sometimes it happens that there are empty
> submenus, and I tried to see if they can't be suppressed
> by mconf (if not explicitely done by the kbuild-language).

I think we still want submenus to be visible if they are not hidden by
any condition in the Kconfig. If the developper did not explicitly add
masking condition, we should *not* try to mask it from the frontends.

However, I agree that entering an empty menu can just be deceptive. If
we could find a way to render an empty menu, and prevent the user from
entering it, then that would be a huge win, I think.

For example, menus are rendered as thus for now:

    This is a submenu  --->

What about representing empty submenus as thus:

    This is a submenu  ----

Also, we have menuconfig which are simply empty if not selected, but can
anyway be entererd like any other submenu:

    [ ] menuconfig entry  --->
        (Always empty when entered if not selected)

which could be similarly rendered as:

    [ ] menuconfig entry  ----

This one is really deceptive, and should be handled in the same scheme
as well.

Any better scheme highly suggested! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2013-05-16 23:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 14:05 [RFC] mconf: suppress empty submenus Dirk Gouders
2013-05-15 14:05 ` [PATCH] " Dirk Gouders
2013-05-16  8:24 ` [RFC] " Dirk Gouders
2013-05-16 23:04 ` Yann E. MORIN [this message]
2013-05-17  4:22   ` Dirk Gouders
2013-05-17 10:28   ` [RFC] mconf: mark empty menus/menuconfigs different form non-empty ones Dirk Gouders
2013-05-17 10:28     ` [PATCH] " Dirk Gouders
2013-05-17 12:42       ` [PATCH v2] mconf/nconf: mark empty menus/menuconfigs different from " Dirk Gouders
2013-05-19 15:14         ` Yann E. MORIN
2013-05-19 19:49           ` [PATCH v3] " Dirk Gouders
2013-05-20 15:50             ` Yann E. MORIN
2013-05-19  9:08     ` [RFC] mconf: mark empty menus/menuconfigs different form " Yann E. MORIN
2013-05-19 16:22       ` Dirk Gouders

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=20130516230404.GB19534@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=dirk@gouders.net \
    --cc=linux-kbuild@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox