9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] scrollbar
Date: Thu,  4 Mar 2004 17:10:21 -0500	[thread overview]
Message-ID: <20040304221021.GD11430@sigint.cs.purdue.edu> (raw)
In-Reply-To: <7eaeeca7ba860f74bdcb2e30cd8f5d3a@plan9.ucalgary.ca>

On Thu, Mar 04, 2004 at 02:51:07PM -0700, andrey mirtchovski wrote:
> Bakul Shah <bakul@BitBlocks.com> wrote:
> > But why use a scrollbar?  Why move the mouse to

I don't, myself.  I turn 'em off on my terminal windows.

> > any edge if all you want to do is to show a
> > different part through a window?  Panning would be
> > so much easier (especially if combined with
> > increasing scroll/pan speed proportional to the
> > distance travelled by the mouse).

Panning is fine for small movements, but there's a tendency to overshoot
big movements because you can't see what's "coming up".  Perhaps if it
were combined with some sort of pop-up indicator of where you are in the
document.

The big problem is that panning doesn't allow for discontinuous movement.
Think of the difference between cassette tapes and compact discs when you
want to skip ahead two songs.

> i've run out of mouse buttons for panning in acme...  unless we do it
> with alt+button :)

Yep.  Meta key chords rule.

> we could go with gestures too -- a clockwise circle with the mouse
> scrolls up, counterclockwise scrolls down; the larger the circle the
> more you scroll (or the faster you rotate the mouse :).

Man, you think you have RSI trouble now...

> this will help touch-screen users since they won't have to hold up to
> 15 buttons at once while hitting the screen with the little pointy
> pen.

True, but they won't be able to see if they've scrolled far enough with
their hand in the way.  I think that's why jog dials were invented.


  reply	other threads:[~2004-03-04 22:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 10:48 Tiit Lankots
2004-03-04 10:54 ` matt
2004-03-04 13:38 ` boyd, rounin
2004-03-04 17:15 ` Rob Pike
2004-03-04 17:22   ` Rob Pike
2004-03-04 17:43   ` rog
2004-03-04 20:21     ` splite
2004-03-05  4:42       ` ron minnich
2004-03-05  4:45         ` Bakul Shah
2004-03-05 18:45         ` [9fans] borders rog
2004-03-05 18:40           ` Charles Forsyth
2004-03-05 18:49             ` rog
2004-03-05 18:44               ` Charles Forsyth
2004-03-05 19:08                 ` rog
2004-03-04 19:04   ` [9fans] scrollbar splite
2004-03-04 19:07     ` Charles Forsyth
2004-03-04 19:17       ` rog
2004-03-04 21:10         ` Charles Forsyth
2004-03-04 22:28           ` boyd, rounin
2004-03-04 19:15     ` rog
2004-03-04 20:56       ` splite
2004-03-04 21:39     ` Bakul Shah
2004-03-04 21:51       ` andrey mirtchovski
2004-03-04 22:10         ` splite [this message]
2004-03-04 22:40         ` boyd, rounin
2004-03-05  0:33           ` Derek Fawcus
2004-03-05 11:33             ` boyd, rounin
2004-03-05  1:16           ` Geoff Collyer
2004-03-05  1:59             ` andrey mirtchovski
2004-03-05  3:45               ` David Presotto
2004-03-05 11:50                 ` 9nut
2004-03-05 14:31                   ` Michael H. Collins
2004-03-05 14:26                 ` Michael H. Collins
2004-03-05  2:00             ` andrey mirtchovski
2004-03-05  9:14               ` Gorka Guardiola Múzquiz
2004-03-05 11:36             ` boyd, rounin
2004-03-04 10:57 Tiit Lankots
2004-03-04 11:05 ` matt
2004-03-04 11:17 ` plan9
2004-03-04 11:15 Tiit Lankots
2004-03-05 14:58 David Presotto
2004-03-05 16:33 ` Michael H. Collins

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=20040304221021.GD11430@sigint.cs.purdue.edu \
    --to=splite@purdue.edu \
    --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).