unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "grischka" <grishka@gmx.de>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: vertical scrollbar error on MS Windows
Date: Wed, 28 Feb 2007 20:45:09 +0100	[thread overview]
Message-ID: <030c01c75b73$9ee4a620$8144fe91@j4f3n1> (raw)
In-Reply-To: jwvslcr6x7s.fsf-monnier+emacs@gnu.org

Stefan Monnier wrote:

> A scrollbar is nothing more than a bunch of pixels that give
> you some rough idea of where you are (and how much of the
> rest there is left to see), along with some way to move with
> the use of a mouse.

Sounds like a somehow applicable description of scrolling
in emacs, to be honest.

> I believe that confining oneself strictly to some analogy to the physical
> world is just plain dumb. What's the benefit, concretely? No user has ever
> complained that she doesn't understand how Emacs scrollbars work just
> because they "slide off the end".  When the thumb slides off the end, all
> users know immediately that it "has slid off the end": they understand it
> completely intuitively.  Only GUI-nitpickers get annoyed that it doesn't
> conform to some model.

I have my doubts whether everybody sees it as you see it. 
As you say one is not confined to one analogy exclusively. 
Also I would not trust a developer with such things anyway.

Other than that I'm still curious to see all that work with 
the intuitive Xaw features added on the scrollbar from the 
other OS.

-- grischka

  reply	other threads:[~2007-02-28 19:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21  0:24 vertical scrollbar error on MS Windows grischka
2007-02-21  8:07 ` Kim F. Storm
2007-02-21 14:02   ` grischka
2007-02-21 19:01 ` Stefan Monnier
2007-02-21 23:36   ` grischka
2007-02-26 19:39     ` Stefan Monnier
2007-02-27 19:19       ` grischka
2007-02-27 20:44         ` David Kastrup
2007-02-27 22:56         ` Stefan Monnier
2007-02-28 19:45           ` grischka [this message]
2007-02-28 21:45             ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2007-02-28 20:01 grischka
2007-02-28 20:54 ` Lennart Borgman (gmail)
2007-03-01  9:11 ` David Kastrup
     [not found] <b5accf970702131432t76036b4erb72cbe4d86e11077@mail.gmail.com>
     [not found] ` <er4kem$ce7$1@sea.gmane.org>
2007-02-19 14:58   ` Kim F. Storm
2007-02-19 16:13     ` Juanma Barranquero
2007-02-19 22:39       ` Kim F. Storm
2007-02-19 23:01         ` Juanma Barranquero
2007-02-19 23:16           ` Nick Roberts
2007-02-19 17:03     ` Lennart Borgman (gmail)
2007-02-19 22:54       ` Peter Tury
2007-02-22 15:07       ` Stephan Hennig
2007-02-22 15:56         ` Jason Rumney
2007-02-22 16:52           ` Kim F. Storm
2007-02-22 17:00           ` Stephan Hennig
2007-02-22 17:28             ` Kim F. Storm
2007-02-22 23:35         ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='030c01c75b73$9ee4a620$8144fe91@j4f3n1' \
    --to=grishka@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).