9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] UI configurability
Date: Tue,  6 Nov 2001 12:07:19 -0500	[thread overview]
Message-ID: <20011106170728.5B6E919A11@mail.cse.psu.edu> (raw)

// The problem here is not that the system can't be configured; the
// problem is that the interface has design problems.  It is much better
// to fix those problems than it is to add configurability.

this is sometimes correct. as in the cases i pointed out, sometimes the
issue is rather that different people legitamatly have different
requirements, for very good and valid physical reasons. some people
find the chording in rio and acme very dificult to use, whereas i find
it amazingly time-saving. should either one of us be forced into a fit
for the other? and simply adding more ways to do things isn't really an
option, either - that's awful design for everyone, as thigns start to
get in each other's way.

i mean, i find the new button 2 menu in rio to be longer than i'd like.
maybe i'm just not smart enough to deal with larger menus proberly, but
i could find snarf and send much more quickly when plumb wasn't in the
way. i'd love to shrink that menu size. but some people need it.

same with color contrast issues. mind you acme's got much better
choices than most editors that touch color, but for some people they
still represent problems. i've seen people with poor vision working on
high-contrast color setting in M$ Windows and X Windows; this helps
them make the computer much more usable, but it gives me migranes in
about 90 seconds (anyone seen one of these and know what i'm talking
about?). again, one size does not fit all.
ア


             reply	other threads:[~2001-11-06 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 17:07 anothy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-05 18:28 anothy
2001-11-06 10:33 ` Thomas Bushnell, BSG

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=20011106170728.5B6E919A11@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --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).