From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: prevent swsusp with PAE
Date: Thu, 31 Aug 2006 17:16:15 -0700 [thread overview]
Message-ID: <20060831171615.6a420025.akpm@osdl.org> (raw)
In-Reply-To: <20060831160546.3309d745.rdunlap@xenotime.net>
On Thu, 31 Aug 2006 16:05:46 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> > > I think what this really points at is a weakness in the menuconfig/xconfig/etc
> > > user interfaces. It should be possible to navigate to the presently-disabled
> > > config option and ask it "why can't I turn you on?".
> >
> > Yes, but I'll still have users asking me "why I can't turn it on" ;-).
>
> menuconfig and xconfig both have Help and Search that can aid
> with that, but I would still use the "comment" keyword also.
Help and Search options aren't much use if you cannot see the option and if
you do not know that it exists.
A better UI design would be to show the unselectable option in some
dimmed-out fashion and then provide an interface which permits the user to
a) query the item to find out why it's not selectable and
b) turn on the depends-on option(s) at the present site, thus making the
present item selectable (ie: not dimmed any more).
I dont't think any of that would require any Kconfig changes - it's purely
a UI thing?
next prev parent reply other threads:[~2006-09-01 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:53 Pavel Machek
2006-08-31 17:43 ` Andrew Morton
2006-08-31 22:35 ` Pavel Machek
2006-08-31 22:48 ` Randy.Dunlap
2006-08-31 22:48 ` Andrew Morton
2006-08-31 22:52 ` Pavel Machek
2006-08-31 23:05 ` Randy.Dunlap
2006-09-01 0:16 ` Andrew Morton [this message]
2006-09-01 0:44 ` Randy.Dunlap
2006-09-02 23:16 ` Pavel Machek
2006-09-01 7:22 ` Jan Engelhardt
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=20060831171615.6a420025.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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
Powered by JetHome