From: "Eric S. Raymond" <esr@thyrsus.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.1.5, more comments
Date: Wed, 18 Apr 2001 09:58:02 -0400 [thread overview]
Message-ID: <20010418095802.B17193@thyrsus.com> (raw)
In-Reply-To: <20010417174407.A6667@thyrsus.com> <5.0.2.1.2.20010418020921.03e99d40@pop.cus.cam.ac.uk>
In-Reply-To: <5.0.2.1.2.20010418020921.03e99d40@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Wed, Apr 18, 2001 at 02:12:00AM +0100
Anton Altaparmakov <aia21@cam.ac.uk>:
> A few comments on cml2 1.1.5 running on my Pentium 133S (make menuconfig,
> fastmode):
>
> - Instantaneous moving up/down! Excellent!
A consequence of getting the incremental-refresh logic right.
> - Thanks for dark blue! The cyan was barely readable. Now all the colours
> are nicely readable. I don't necessarily like your choice of colours but as
> long as I can read the text, that's fine.
It's a difficult balancing act. A lot of the people asking for color changes
aren't aware of some of the constraints -- one of them being that 12% of the
male population has red-green color blindness. Blue turns out to be about the
only color that people with any form of color blindness can recognize.
> - When I set something to yes it goes green. When I then set something else
> to yes the new one goes green, too, but the old one also remains green. Is
> this intended? (i.e. does green mean "already visited" or something like
> that?) Also, on the CPU selection menu, it started off with two of the CPUs
> already in green (but only one with a yes). Is that a feature or a bug?
That's right. Green means "visited or set".
> - Moving left/right can still be quite painfully slow...
I know. The basic problem here is that the configurator has to recalculate
visibilities for every item in the new nenu. I have some ideas for speed-
tuning this.
> - Setting options is sometimes very slow, sometimes ok... (depends on
> complexity of underlying rules I guess)
Yes. There is at least one more major speedup I may be able to get out
of this.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Whether the authorities be invaders or merely local tyrants, the
effect of such [gun control] laws is to place the individual at the
mercy of the state, unable to resist.
-- Robert Anson Heinlein, 1949
prev parent reply other threads:[~2001-04-18 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 21:44 CML2 1.1.6, aka "I think I should have stayed in bed this morning." Eric S. Raymond
2001-04-18 1:12 ` CML2 1.1.5, more comments Anton Altaparmakov
2001-04-18 13:58 ` Eric S. Raymond [this message]
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=20010418095802.B17193@thyrsus.com \
--to=esr@thyrsus.com \
--cc=aia21@cam.ac.uk \
--cc=kbuild-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.