unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "grischka" <grishka@gmx.de>
To: <emacs-devel@gnu.org>
Subject: Re: gtk scroll bar deficiency
Date: Thu, 14 Jun 2007 13:56:18 +0200	[thread overview]
Message-ID: <006d01c7ae7b$2516a540$d10990d4@j4f3n1> (raw)
In-Reply-To: 87lkemki35.fsf@ambire.localdomain

> i think the point is that a different metaphor pleases other
> people.  if the mechanisms that support your preferred metaphor
> cannot support another, that is a deficiency in the generality of
> those mechanisms.
> 
> "but they were not designed to be general."
> 
> art of design is finding balance between undesired (maintenance
> burden) and desired (customizable) generality.  it is ok to be
> artistically deficient (most of us are so by default!), but there
> is no escaping the art critics -- they are everywhere.
> 
> thi

Simple and clear does not mean artistically deficient. Often the
contrary is true. I personally think the GUI designers knew what 
they were doing. Nobody wants to see the same scrollbars behave 
differently in every other application.

Why not be realistic? Do you think scrollbar toolkits will change 
anytime near in the future? If not, what is the point to spend 
time in nagging at other peoples decisions.

In the meantime, whats with emacs scrolling through inlined 
images, varying fontheights, etc. Sooner or later you will need 
a better internal infrastructure, and once you have it driving 
the standard scrollbars will be no problem at all, either.

-- grischka

  reply	other threads:[~2007-06-14 11:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14  8:52 gtk scroll bar deficiency grischka
2007-06-14  9:20 ` Thien-Thi Nguyen
2007-06-14 11:56   ` grischka [this message]
2007-06-14 17:21   ` grischka
2007-06-14 18:22     ` David Reitter
2007-06-14 20:30       ` Jason Rumney
2007-06-15 11:41       ` grischka
2007-06-15 14:48         ` Stefan Monnier
2007-06-18 13:32           ` grischka
2007-06-14 19:05     ` Stefan Monnier
2007-06-15 11:46       ` grischka
2007-06-15 14:56         ` Stefan Monnier
2007-06-15 15:56           ` Sam Steingold
2007-06-15 18:35             ` Stefan Monnier
2007-06-15 18:58               ` Sam Steingold
2007-06-14  9:24 ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2007-06-11 18:05 Sam Steingold
2007-06-11 19:25 ` Stefan Monnier
2007-06-11 19:54   ` Sam Steingold
2007-06-11 21:09     ` Stefan Monnier
2007-06-12  5:52     ` Jan Djärv
2007-06-12  5:57       ` Ralf Angeli
2007-06-12  6:06         ` Jan Djärv
2007-06-12  6:12           ` Ralf Angeli
2007-06-12  7:40             ` Jan Djärv
2007-06-15 20:51               ` Ralf Angeli
2007-06-12 11:09         ` David Reitter
2007-06-12  8:49       ` Andreas Schwab
2007-06-12  9:10         ` Jan Djärv
2007-06-12 13:04       ` Sam Steingold
2007-06-12 13:11         ` David Kastrup
2007-06-12 13:19           ` Sam Steingold
2007-06-12 15:13         ` Stefan Monnier
2007-06-12 22:38     ` Davis Herring

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='006d01c7ae7b$2516a540$d10990d4@j4f3n1' \
    --to=grishka@gmx.de \
    --cc=emacs-devel@gnu.org \
    /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).