From: Marko Kreen <marko@l-t.ee>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: linux-kernel@vger.kernel.org
Subject: comments on CML 1.1.0
Date: Sat, 14 Apr 2001 15:04:21 +0200 [thread overview]
Message-ID: <20010414150421.A28066@l-t.ee> (raw)
In-Reply-To: <200104140317.f3E3Hv805992@snark.thyrsus.com>
In-Reply-To: <200104140317.f3E3Hv805992@snark.thyrsus.com>; from esr@snark.thyrsus.com on Fri, Apr 13, 2001 at 11:17:57PM -0400
Using CML2 1.1.0 'menuconfig' on clean 2.4.3 (mach is PPro 180)
Suggestions:
* the 'N' should be shown as ' ' as in menuconfig - it is
visually much better to get overview of whole screenful.
'Y'/'M' and 'N' are basically of 'same size' so you must look
directly on letter to understand what it is - not good.
* the menuconfig had nice shortcut: when you pressed 'm' on
[YN] field, it put 'y' there without questions. So you could
use only 2 keys to configure one screen: 'n/m'. this meant
you did not need to move fingers around and think about it
so much - big thing when you are not touch-typer...
* the colors are hard to see (red/blue on black). Probably
matter of terminal settings. I do not have any productive
ideas tho... Probably to get best experience to as much
people as possible the less colors are used the better.
The 'blue: last visited submenu' is unnecessary. Especially
because it later turns green... And the 'red' vs. 'green'
thing. I guess the green should be used for 'visited entries'
too. Now the red means like 'Doh. So I should not have
touched this?'. Confusing.
In other words: if there are too much colors, they become
a thing that should be separately learned, not a helpful
aid.
All this IMHO ofcourse. Colors are 'matter of taste' thing
so there probably is not exact Rigth Thing.
Bugs/complaints:
* aic7xxx is not updated (defaults: are 8/5 should be 253/5000)
(this from arch/i386/defconfig maybe?)
* 'IDE chipset support' nesting is very confusing - compare
to menuconfig. I would say even 'wrong'...
(eg. 'PIIXn tuning' is is under 'PIIXn support' which is not
under 'ATA works in progress'.
* screen is redrawn after _every_ keystroke - not only in moving
around, but even when you are on input field...
* input field: when there is some default and I start typing it
should either clear it or append.
--
marko
next prev parent reply other threads:[~2001-04-14 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-14 3:17 CML 1.1.0, aka "I feel the need...the need for speed." Eric S. Raymond
2001-04-14 13:04 ` Marko Kreen [this message]
2001-04-14 15:58 ` comments on CML 1.1.0 jeff millar
2001-04-14 17:38 ` CML2 1.1.0 bug and snailspeed Anton Altaparmakov
2001-04-14 17:56 ` Eric S. Raymond
2001-04-15 10:48 ` Anton Altaparmakov
2001-04-15 17:59 ` Eric S. Raymond
2001-04-15 23:55 ` Anton Altaparmakov
2001-04-16 17:02 ` Eric S. Raymond
2001-04-14 19:51 ` comments on CML 1.1.0 Eric S. Raymond
2001-04-17 1:31 ` Harald Welte
2001-04-17 14:24 ` Eric S. Raymond
2001-04-15 13:20 ` Daniel Stone
2001-04-14 20:49 ` Eric S. Raymond
2001-04-24 0:21 ` Oliver Xymoron
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=20010414150421.A28066@l-t.ee \
--to=marko@l-t.ee \
--cc=esr@snark.thyrsus.com \
--cc=linux-kernel@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