linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Sam Ravnborg <sam@ravnborg.org>, Al Boldi <a1426z@gawab.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/5] USB Kconfig: Select SCSI for USB Mass Storage	support
Date: Sun, 06 Jan 2008 13:32:35 +0100	[thread overview]
Message-ID: <4780CA63.50703@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080106115941.GB2082@does.not.exist>

Adrian Bunk wrote:
> On Sun, Jan 06, 2008 at 12:29:46PM +0100, Stefan Richter wrote:
>> Adrian Bunk wrote:
>>> Duplicating the structure in each UI should be an improvement?
>>>
>>> Hardly.
>> What do you mean?
...
> You said:
> "The graphic UIs including menuconfig currently work best for tree-like 
>  dependencies"
> 
> That's true.
> 
> And the dependency graph can't be a tree.
> 
> Currently, defining the ordered tree the UIs present to the user is done 
> _once_ in kconfig.
> 
> Our UIs either show this tree as a tree or go through the tree 
> depth-first and present the options in this order to the user.

All correct.

> And I think your main misunderstanding is that you think the 
> dependencies alone would carry enough information for allowing an UI to 
> present the options in a way not worse than it's currently done - that's 
> simply not true.

No, the dependency relationships alone do not carry enough information.
  I am aware of that.

For example, we certainly want groupings or tags such as "option is
(directly) related to USB hardware", "filesystems related option",
"option is for debugging purposes" etc..  We currently provide hints
like this via the 'menu' keyword.  We also want help texts per option
and per group of options.

However, there is ultimately not a single most logical way to group
options.  There could be groups which would overlap.  The grouping per
'menu' provides only one fixed non-overlapping grouping.
-- 
Stefan Richter
-=====-==--- ---= --==-
http://arcgraph.de/sr/

  reply	other threads:[~2008-01-06 12:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 15:41 [PATCH 2/5] USB Kconfig: Select SCSI for USB Mass Storage support Al Boldi
2008-01-05 18:42 ` David Brownell
2008-01-05 19:30 ` Randy Dunlap
2008-01-05 21:03   ` Adrian Bunk
2008-01-05 21:09     ` Sam Ravnborg
2008-01-05 23:22       ` Randy Dunlap
2008-01-05 23:45         ` Adrian Bunk
2008-01-06  0:35           ` Stefan Richter
2008-01-06  0:58             ` Adrian Bunk
2008-01-06 11:29               ` Stefan Richter
2008-01-06 11:59                 ` Adrian Bunk
2008-01-06 12:32                   ` Stefan Richter [this message]
2008-01-06 12:58                     ` Adrian Bunk
2008-01-06 13:23                       ` Stefan Richter
2008-01-06 12:18               ` Stefan Richter
2008-01-06 12:37                 ` Adrian Bunk
2008-01-06 13:13                   ` Stefan Richter
2008-01-06 13:38                     ` Adrian Bunk
2008-01-06 13:55                       ` Sam Ravnborg
2008-01-06 13:57                       ` Stefan Richter
2008-01-06 14:45                     ` david
2008-01-06 13:41                       ` Stefan Richter
2008-01-06 15:05                         ` david
2008-01-06 14:08                           ` Stefan Richter
2008-01-06 17:11                           ` Alan Stern
2008-01-06 18:07                             ` Stefan Richter
2008-01-06  1:01             ` Randy Dunlap
2008-01-06 11:54         ` Stefan Richter
2008-01-06 12:05           ` Adrian Bunk
2008-01-06 12:41             ` Stefan Richter
2008-01-06  5:03       ` Al Boldi
2008-01-06 14:39         ` Stefan Richter
2008-01-06 17:07           ` Al Boldi
2008-01-06 17:50             ` Stefan Richter
2008-01-06 18:01               ` Stefan Richter
2008-01-06 18:23               ` Sam Ravnborg
2008-01-05 20:40 ` Stefan Richter

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=4780CA63.50703@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=a1426z@gawab.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).