9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] interesting(?) widgets idea
Date: Fri, 15 Jul 2011 21:41:23 +0100	[thread overview]
Message-ID: <20110715214123.18186ee1@lahti.ethans.dre.am> (raw)
In-Reply-To: <18A0ABD5-F005-4295-B279-4789A728736D@9srv.net>

On Wed, 13 Jul 2011 10:45:38 -0400
Anthony Sorace <a@9srv.net> wrote:

> On Jul 13, 2011, at 10:16, Wes Kussmaul <wes@authentrus.com> wrote:
>
> > Isn't this a perfect case for letting the user set a parameter,
> > depending upon his/her preference?
>
> No. The choice is between two very different user interaction models. Nobody has claimed that having widgets filling what would otherwise be margins and having them *not* fade would be a good plan. It'd be like setting a parameter to determine whether your editor acted like sam or acme - just pick which to run, instead.

I commented that Plan 9 scrollbars are (more or less) light enough to be like margins themselves, so we already have that as default. If they're too contrasty, that can always be hacked (probably in libframe).

>
> I'm surprised and a bit disappointed that with all the talk I've seen on this topic over the years there haven't been more actual experiments (rio -i being the most ambitious I can think of). The rio code is nice to work with - pick it apart and get hacking.

Yeah. Experimenting has certainly been on my list for a while, but I wasn't well enough to try to understand the libframe code. I'm a lot better now, and experiemting with libframe and rio is closer to the top of my list than ever.



  reply	other threads:[~2011-07-15 20:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 14:56 Peter A. Cejchan
2011-07-11 15:14 ` simon softnet
2011-07-11 15:25   ` Peter A. Cejchan
2011-07-11 15:21 ` hiro
2011-07-11 15:23   ` hiro
2011-07-11 15:35   ` Peter A. Cejchan
2011-07-11 15:43     ` dexen deVries
2011-07-11 16:12       ` Peter A. Cejchan
2011-07-11 16:56         ` Jacob Todd
2011-07-11 17:21           ` Peter A. Cejchan
2011-07-11 17:25             ` ron minnich
2011-07-11 17:28             ` dexen deVries
2011-07-12  6:15               ` Peter A. Cejchan
2011-07-11 17:28             ` Lyndon Nerenberg
2011-07-11 17:28             ` andrey mirtchovski
2011-07-12  8:23 ` Sergey Kish
2011-07-12  9:18   ` Peter A. Cejchan
2011-07-12 12:18 ` Ethan Grammatikidis
2011-07-12 12:36   ` dexen deVries
2011-07-12 13:00     ` yy
2011-07-12 13:21       ` Jack Norton
2011-07-12 13:40     ` Ethan Grammatikidis
2011-07-12 14:31       ` dexen deVries
2011-07-12 14:56         ` Ethan Grammatikidis
2011-07-12 15:26           ` dexen deVries
2011-07-13  6:02             ` Peter A. Cejchan
2011-07-13  6:12               ` Bruce Ellis
2011-07-14 17:12               ` Yaroslav
2011-07-14 17:22                 ` dexen deVries
2011-07-13 13:43             ` Jack Norton
2011-07-13 14:16               ` Wes Kussmaul
2011-07-13 14:45                 ` Anthony Sorace
2011-07-15 20:41                   ` Ethan Grammatikidis [this message]
2011-07-15 20:34               ` Ethan Grammatikidis
2011-07-15 20:59                 ` Wes Kussmaul
2011-07-12 20:52   ` Akshat Kumar
2011-07-13  6:15   ` Peter A. Cejchan
2011-07-13  6:23     ` Bruce Ellis
2011-07-15 20:45     ` Ethan Grammatikidis

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=20110715214123.18186ee1@lahti.ethans.dre.am \
    --to=eekee57@fastmail.fm \
    --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).