From: Rene Herman <rene.herman@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kconfig - a suggestion how to fix the select issue
Date: Sun, 04 May 2008 21:28:54 +0200 [thread overview]
Message-ID: <481E0E76.3060900@gmail.com> (raw)
In-Reply-To: <20080504071041.GA15315@uranus.ravnborg.org>
On 04-05-08 09:10, Sam Ravnborg wrote:
> Today we have two ways to express/solve dependencies.
>
> Top-down we have "depends on"
> and bottom up we have "select".
>
> The "depends on" dependencies at the same
> time impact the visibility of a symbol.
> A symbol with "depends on" not satisfied are not
> visible and thus not shown in menuconfig.
I've always really disliked the visibility thing. I believe it's not really
the core issue here but regardless of anything else, could we not "grey out"
non-selectable options with its helpt text still available? That's much more
the standard UI paradigm.
Rene.
next prev parent reply other threads:[~2008-05-04 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 7:10 kconfig - a suggestion how to fix the select issue Sam Ravnborg
2008-05-04 8:11 ` Adrian Bunk
2008-05-04 8:27 ` Sam Ravnborg
2008-05-04 9:04 ` Adrian Bunk
2008-05-04 10:38 ` Sam Ravnborg
2008-05-04 11:55 ` Adrian Bunk
2008-05-04 12:17 ` Sam Ravnborg
2008-05-04 12:57 ` Adrian Bunk
2008-05-04 12:37 ` Oleg Verych
2008-05-04 10:12 ` Bernd Petrovitsch
2008-05-04 17:59 ` Matthias Schniedermeyer
2008-05-04 12:55 ` David Collier-Brown
2008-05-04 15:01 ` Oleg Verych
2008-05-04 19:28 ` Rene Herman [this message]
2008-05-04 19:32 ` Sam Ravnborg
2008-05-04 20:14 ` Bernd Eckenfels
2008-05-06 8:19 ` Jan Engelhardt
2008-05-06 15:52 ` Oleg Verych
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=481E0E76.3060900@gmail.com \
--to=rene.herman@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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.