9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme without a heavy grid (SFW)
Date: Wed, 30 Sep 2009 16:41:14 -0500	[thread overview]
Message-ID: <d50d7d460909301441i6ee499det3a0ba85c3df47d19@mail.gmail.com> (raw)
In-Reply-To: <4AC3C2F0.6000102@0x6a.com>

On Wed, Sep 30, 2009 at 15:43, Jack Norton <jack@0x6a.com> wrote:
> Jason Catena wrote:
>> A quick edit frees acme from its "heavy grid prison", a la Tufte.
>> https://dl.getdropbox.com/u/502901/acmenogrid.jpg
>
> How about no grid whatsoever (while you're at it)?

I believe in a subtle or invisible grid to lay out text in columns,
divide columns into files, directories, and output, and whitespace to
separate them.  I seek to minimize, not deconstruct.

> There is plenty of contrast there to forego any kind of hard devisions.

I agree that all you really need are left-justified columns of text to
show a grid (eg a newspaper).  The remaining structural elements
(dirty button, scroll bar) are functional, so it would change acme too
much to remove or hide them, and would be counter-productive.

I used wily for a few years and took out the heavy black horizontal
and vertical window lines from it as well.  In comparison, Rob's color
scheme provides much better separation of tags and windows, so
removing them has less effect on the interface.

> However, I end up with the same conclusion: why?

To increase the ratio of visible, contrasting pixels used to indicate
data, program state, and commands, to pixels used to dress the screen.

> Is the 'grid' that distracting?

The black lines around each window currently have the most contrast
(black on beige and light blue), and largest scope (right to left, top
to bottom) of any element on the screen.  By giving them the least
contrast (white on beige and light blue), text and commands become
more prominent.  The lack of lines between tags serves as leading
(vertical space between horizontal lines), making each tag easier to
read.

> Also, if you have two text files open side-by-side, and your
> lines are long enough to wrap, you would have a glob of incomprehensible
> text in the middle.

I did not remove the scroll bars or dirty bits, which serve as gutters
between columns.  I agree that without them, run-on text in adjacent
columns would be very difficult to read.  Fortunately, their
functionality makes them easy to keep.

> I think at least a moderately thick grid is a necessary evil.

I agree that you have to have a grid.  I think we disagree on how
heavy and obvious you make its structural lines.

> -jack

Jason Catena



  reply	other threads:[~2009-09-30 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 23:25 Jason Catena
2009-09-30 20:43 ` Jack Norton
2009-09-30 21:41   ` Jason Catena [this message]
2009-10-01  0:44   ` Ethan Grammatikidis
2009-10-01 16:49 ` J.R. Mauro
2009-10-01 17:18   ` [9fans] (no subject) Pablo Alonso Salas Alvarez

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=d50d7d460909301441i6ee499det3a0ba85c3df47d19@mail.gmail.com \
    --to=jason.catena@gmail.com \
    --cc=9fans@9fans.net \
    /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).