9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] panning or scrolling, page(1)
Date: Sun,  4 Mar 2001 19:15:23 +0000	[thread overview]
Message-ID: <20010304180958.D4E68199E3@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

i like the panning model too, but i don't tend to view very large
images.

when you've got a large image (many times the size of the area you can
see), panning can be a bit of a problem because you can only go a small
distance at once.

i.e. if i'm at the bottom left of a large image and i want to go to the top
right, it might take me 10 or so "click & pan" mouse movements to get
there.

but for images that size, maybe a different interface is called for
anyway.

my last job was writing radio propagation prediction software, which
involved the viewing of large maps (e.g. the entire of the UK with one
height sample every 100m). i once accidentally created quite a nice
viewing interface when i set the map to be always centred around the
transmitter.

normally, you could drag transmitters around with the mouse, and i
hadn't yet disabled this, so when i dragged the transmitter, it moved,
but the map kept up, giving the nice sensation of flying over the
landscape. (as long as i kept wiggling the mouse...)

maybe that kind of interface might sit better with the panning that
page uses (e.g. middle button "marks the spot", and map keeps panning
at a speed proportional to the vector from the spot to the current
mouse position).  i always find it a little disconcerting that the
middle button quits page so abruptly anyway.

  cheers,
    rog.


[-- Attachment #2: Type: message/rfc822, Size: 1671 bytes --]

To: cse.psu.edu!9fans
Subject: Re: [9fans] panning or scrolling, page(1)
Date: Fri, 2 Mar 2001 21:49:26 -0500
Message-ID: <20010303024929.04C5E199DC@mail.cse.psu.edu>

I strongly prefer the panning model to the scrolling model. It's so much
easier to use I wish it were available everywhere.  Are you really asking for
some indication of what part of the image is visible?  Scroll bars provide
that at the cost of a crappy interface, but there's no reason at all why a
panning interface can't give you some indication of what subset of the
entire object you're viewing.

-rob

             reply	other threads:[~2001-03-04 19:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-04 19:15 rog [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-05  1:10 okamoto
2001-03-03  2:49 rob pike
2001-03-03  3:58 ` Fariborz 'Skip' Tavakkolian
2001-03-02  5:19 okamoto

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=20010304180958.D4E68199E3@mail.cse.psu.edu \
    --to=rog@vitanuova.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).