From: "Eric S. Raymond" <esr@thyrsus.com>
To: John Cowan <cowan@mercury.ccil.org>
Cc: james rich <james.rich@m.cc.utah.edu>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] CML2 1.1.3 is available
Date: Tue, 17 Apr 2001 10:38:56 -0400 [thread overview]
Message-ID: <20010417103856.A27762@thyrsus.com> (raw)
In-Reply-To: <20010416205556.A22960@thyrsus.com> <E14pTOH-0007ex-00@mercury.ccil.org>
In-Reply-To: <E14pTOH-0007ex-00@mercury.ccil.org>; from cowan@mercury.ccil.org on Tue, Apr 17, 2001 at 07:11:25AM -0400
John Cowan <cowan@mercury.ccil.org>:
> > If there were already a library in ths stock Python distribution to digest
> > .Xdefaults files I might consider this. Perhaps I'll write one. But I'm
> > not going to bulk up the CML2 code with this marginal feature.
>
> Then support a private mechanism if you must. But leaving colors hard-coded
> in the application is just as bad as leaving strings hard-coded there, and
> for the same reasons: it's a point that needs to be adjustable for
> accessibility. The whole point of CML2 is to make kernel configuration something
> that Aunt Tillie (or a reasonable facsimile thereof) can do, and we are
> all Aunt Tillies from time to time. That includes differing standards of
> readability, quite apart from the differences in monitors that make
> a Mac user's *red* look more like *orange* to me (and CML2 will be
> used, perhaps even more often used, off stock x86 hardware).
>
> Without counting, I estimate that 50% of the problem (I won't say "bug"
> in this context) reports you have had since 1.0.0 have been about colors.
> The more users you get, the more such complaints there will be. Nail
> this one to the wall before people start demanding contradictory changes.
>
> If you don't have a full X resources parser, then do a trivial scan of
> just .Xdefaults and look for a few fixed cases like
>
> CMLConfigure*YColor: 0xrrbbgg
> CMLConfigure*NColor: 0xrrbbgg
>
> etc. etc. Or provide a private .rc file. Or *something*.
Unfortunately, life is not so simple.
X speaks RRBBGG -- or does it? Suppose the user isn't running in
24-bit true-color mode; do I do my own dithering or quantization? The
terminal emulators only know about the 16 EGA colors. So, should I
support separate resource formats for X and menuconfig cases? But
wait! The Linux console does RRBBGG.
Other possibility: support only the 16 EGA colors by name. But if I do that,
some of the X colors are just *wrong* on standard gray background (cyan is
a good example).
There's no way to get this right. So I choose to get it wrong in a simple
way rather than a complex, costly way.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
"Extremism in the defense of liberty is no vice; moderation in the
pursuit of justice is no virtue."
-- Barry Goldwater (actually written by Karl Hess)
next prev parent reply other threads:[~2001-04-17 14:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 21:42 CML2 1.1.3 is available Eric S. Raymond
2001-04-16 21:53 ` [kbuild-devel] " John Cowan
2001-04-16 22:28 ` james rich
2001-04-17 0:55 ` Eric S. Raymond
2001-04-17 1:28 ` Peter Samuelson
2001-04-17 3:20 ` Eric S. Raymond
2001-04-17 8:06 ` Andrew Pimlott
2001-04-17 10:25 ` Olaf Titz
2001-04-17 11:11 ` [kbuild-devel] " John Cowan
2001-04-17 14:38 ` Eric S. Raymond [this message]
2001-04-17 15:23 ` CMLConfigurator skins (was: CML2 1.1.3 is available) John Cowan
2001-04-17 16:14 ` CML2 1.1.3 is available Peter Samuelson
2001-04-17 13:14 ` [kbuild-devel] " Mike A. Harris
2001-04-19 23:20 ` Adam Sampson
2001-04-22 0:03 ` Albert D. Cahalan
2001-04-16 22:00 ` Steven Cole
2001-04-16 22:06 ` Eric S. Raymond
2001-04-16 22:26 ` Steven Cole
2001-04-17 7:15 ` Marko Kreen
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=20010417103856.A27762@thyrsus.com \
--to=esr@thyrsus.com \
--cc=cowan@mercury.ccil.org \
--cc=james.rich@m.cc.utah.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox