9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: pavlovetsky@gmail.com
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Colors and other fun
Date: Thu, 28 Jun 2007 08:52:54 +0000	[thread overview]
Message-ID: <1182989850.281545.170520@c77g2000hse.googlegroups.com> (raw)
In-Reply-To: <08d52a5efa996c205c60302e84f5cbcc@coraid.com>

I would like to point the attention of the audience to the notion,
which Rob made back in 2003:

From: r...@mightycheese.com (Rob Pike)
Date: Sep 16 2003, 8:49 am
Subject: g++
To: comp.os.plan9


> This is an interesting point. Plan 9 esthetics are really nice. colors,
> fonts, and so on just "look good". Who did all that?

glad you like it.  really glad.  most people say something rude about
it.

i can take no credit for the fonts except for having the good luck to
know
chuck bigelow and kris holmes well enough to ask them to do a deal
with
bell labs and let us use their fonts.  the postscript fonts used in
the
manual,
which are related to the screen fonts (primarily those used in acme),
were
the first font designed specifically for unicode.  i also rather like
the screen
fonts, which were also maybe the first.

the clean appearance of the screen comes mostly from laziness, but the
color scheme is (obviously) deliberate. the intent was to build on an
observation by edwardtuftethat the human system likes nature and
nature
is full of pale colors, so something you're going to look at all day
might best
serve if it were also in relaxing shades.  renee french helped me with
the
specifics of the color scheme (she's a professional illustrator and my
color
vision is suspect), once i'd figured out how i wanted it to look.
there are
still some features of the color system that i put in that i think no
one has
ever noticed.  that's a good thing, in my opinion; the colors should
fade
away, if you'll pardon the expression.

having used other systems with different approaches to color screens,
most especially windows XP (extra pukey), i thinktuftewas right.

-rob


  parent reply	other threads:[~2007-06-28  8:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 18:59 [9fans] " Russ Cox
2007-06-27 19:13 ` Tim Wiess
2007-06-27 21:25 ` Charles Forsyth
2007-06-27 15:41   ` john
2007-06-27 21:56     ` erik quanstrom
2007-06-27 16:18       ` john
2007-06-27 22:06       ` Kris Maglione
2007-06-28  8:52       ` pavlovetsky [this message]
2007-06-28 13:20         ` [9fans] " Markus Sonderegger
2007-06-28 19:02           ` Markus Sonderegger
2007-06-28 19:09             ` Markus Sonderegger
2007-06-28 15:50         ` Jack Johnson
2007-06-29  3:25           ` john
2007-06-29 13:09           ` Jack Johnson
2007-06-27 21:48 ` [9fans] " Markus Sonderegger

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=1182989850.281545.170520@c77g2000hse.googlegroups.com \
    --to=pavlovetsky@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).