From: Willy Tarreau <w@1wt.eu>
To: Nir Tzachar <tzachar@grad120a.cs.bgu.ac.il>
Cc: linux-kernel@vger.kernel.org, bzolnier@gmail.com,
zippel@linux-m68k.org, linux-kbuild@vger.kernel.org,
ariveira@gmail.com, rdunlap@xenotime.net,
kosaki.motohiro@jp.fujitsu.com, 7eggert@gmx.de,
Nir Tzachar <nir@tzachar.com>
Subject: Re: [PATCH] ncurses based config V2
Date: Fri, 5 Sep 2008 21:59:30 +0200 [thread overview]
Message-ID: <20080905195930.GA27913@1wt.eu> (raw)
In-Reply-To: <1220603220-17090-1-git-send-email-nir@tzachar.com>
Hello,
On Fri, Sep 05, 2008 at 11:27:00AM +0300, Nir Tzachar wrote:
> Changes:
> 1) Fixed segfaults in help window.
> 2) Removed the instructions window, made the instructions appear as a button
> which displays a popup window.
> 3) Added hot keys support. As ncurses does not support several colors inside
> a menu, keys are highlighted using "()".
> 4) Optimized for 80x24 terminals.
> 6) Fixed zconf.y to use _menu_init
> 7) added nconfig to "make help"
> 8) Misc fixes.
>
> Comments are appreciated.
OK, I've just tried it. Here are the first comments I can make :
- colors are too dark. Cyan on black is barely readable, red on black is
almost unreadable and blue on black is not readable at all, I have to
switch off the light to read it. Most often you'll see light shades of
grey (even white) in interfaces because it's hard to see dark shades,
and bright flashy letters would dazzle and be seen as fuzzy. Many colors
are perfectly readable on while or even light grey (except yellow and
sometimes cyan). Blue backgrounds were often used under DOS and were
OK with almost all colors except red (well-known eye focus problem).
But there was a trick, pixels were very large in 640x200, nowaydays
we have small pixels and letters are not much readable anymore on blue
backgrounds. For your tests, you can try to load
xterm -bg <color> -fg <color> and ensure that you're using a medium
font (tickness of 1-pixel).
- pressing arrows too fast regularly escapes (probably because of the
ESC prefix, I don't know). This is rather strange, because no other
application does this to me. Is there a specific initialization
sequence with ncurses to state that arrows should return special codes
instead of the ESC prefix ? (I have no idea)
- entering text in boxes (eg: local version) does not move the cursor,
it remains at the beginning of the line. If I press any arrow, the
box immediately closes (most likely the Esc prefix again).
- in the input boxes, spaces are missing aroung the title, which touches
the frame (eg: Local version again).
- in "instructions", it's not explained how to leave that box. I found
both Enter and Esc to work, but a last line with a small message would
be better.
- I noticed I was tempted a lot to press "?" to get help, but the key is
not bound. It would be nice to have it bound to Help since make oldconfig
and menuconfig to both report help that way.
- I'm not convinced that the parenthesis around hotkeys make the menu
that much readable, especially when there are lots of short words or
even acronyms. Eg :
[ ] (U)TS namespace
[ ] (I)PC namespace
[ ] (U)ser namespace (EXPERIMENTAL)
[ ] (P)ID Namespaces (EXPERIMENTAL)
I don't know if there is something such as a bold attribute in ncurses,
it would make sense to use it IMHO because you don't force a color on
people's terms, you rely on the style which works well for them.
I'm sorry I don't go further for now, the arrows causing frequent exits is
too bothersome, I've started it about 30 times just for this report, it's
too hard to navigate. I hope that the points above are already helpful.
Regards,
Willy
next prev parent reply other threads:[~2008-09-05 20:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 19:11 [PATCH] ncurses based config Nir Tzachar
2008-09-03 19:38 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:02 ` Randy.Dunlap
2008-09-03 20:03 ` Randy.Dunlap
2008-09-03 20:18 ` Bartlomiej Zolnierkiewicz
2008-09-03 20:29 ` Alejandro Riveira Fernández
2008-09-04 15:02 ` Bartlomiej Zolnierkiewicz
[not found] ` <9b2db90b0809032155h6ed5df9ey846de96779022d11@mail.gmail.com>
2008-09-04 15:28 ` Randy.Dunlap
2008-09-04 4:22 ` KOSAKI Motohiro
2008-09-04 10:36 ` Alejandro Riveira Fernández
2008-09-05 8:27 ` [PATCH] ncurses based config V2 Nir Tzachar
2008-09-05 13:49 ` Alejandro Riveira Fernández
2008-09-05 19:59 ` Willy Tarreau [this message]
2008-09-06 5:41 ` Nir Tzachar
2008-09-14 10:52 ` Willy Tarreau
2008-09-17 11:58 ` Nir Tzachar
2008-11-24 18:44 ` Sam Ravnborg
2008-11-25 2:33 ` Roman Zippel
2008-11-25 8:04 ` Nir Tzachar
2008-11-25 16:02 ` Roman Zippel
2008-11-25 8:01 ` Nir Tzachar
2008-11-25 8:11 ` Sam Ravnborg
2008-11-25 12:35 ` Nir Tzachar
2008-11-29 21:40 ` sss Nir Tzachar
2008-11-29 21:40 ` [PATCH] nconfig V3 Nir Tzachar
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=20080905195930.GA27913@1wt.eu \
--to=w@1wt.eu \
--cc=7eggert@gmx.de \
--cc=ariveira@gmail.com \
--cc=bzolnier@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@tzachar.com \
--cc=rdunlap@xenotime.net \
--cc=tzachar@grad120a.cs.bgu.ac.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox