Message-ID: <20080905195930.GA27913@1wt.eu>
Date:	Fri, 5 Sep 2008 21:59:30 +0200
From:	Willy Tarreau <w@....eu>
To:	Nir Tzachar <tzachar@...d120a.cs.bgu.ac.il>
Cc:	linux-kernel@...r.kernel.org, bzolnier@...il.com,
	zippel@...ux-m68k.org, linux-kbuild@...r.kernel.org,
	ariveira@...il.com, rdunlap@...otime.net,
	kosaki.motohiro@...fujitsu.com, 7eggert@....de,
	Nir Tzachar <nir@...char.com>
Subject: Re: [PATCH] ncurses based config V2

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists