unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: gtk scroll bar: upstream bug report
Date: Wed, 13 Jul 2011 09:39:39 +1000	[thread overview]
Message-ID: <CAC=50j-fC3eCHnfvbEfZLNJ3dNSdjT+8TG+6ceRp2ChyQ2P9bQ@mail.gmail.com> (raw)
In-Reply-To: <4E1C6E4C.6080405@swipnet.se>

On Wed, Jul 13, 2011 at 1:54 AM, Jan Djärv <jan.h.d@swipnet.se> wrote:
>
>
> Miles Bader skrev 2011-07-12 11.04:
>>
>> Richard Riley<rileyrg@googlemail.com>  writes:
>>>>
>>>> I got the impression that scrollbars is even further away from the
>>>> Emacs model nowdays.  The minimum size requirement for the scroll
>>>> bar thumb is more common with new fancy themes.  The Emacs model is
>>>> simply incompatible.
>>>
>>> How is it incompatible? There were many positive suggestions in that
>>> old thread.
>>
>> Certainly the impression I got from the old discussions was that it
>> wasn't so much that it was _difficult_ to support the Emacs model, but
>> rather that they wanted to _prevent_ apps from using such a model
>> because they thought it was bad (for the user?).
>
> I think they want applications to behave the same, and the Emacs model is
> late to the game (for Gtk+).  So there is little reason to switch.
>
>        Jan D.
>
>
>

My interaction with GTK+ developers supports this as well. There
appears to be a fairly strong GUI design philosophy underlying GTK+
which tries to enforce what they believe are good UI design principals
and ensure consistency across apps which use the toolkit. I think this
is a good thing, but it does mean we are likely to run up against UI
'reatures' which traditionally, emacs has supported that will not be
possible under this toolkit. Whether the inability to support a
feature udner a toolkit represents a bug from the emacs perspective is
uncertain (I don't think it is a bug), but I certainly would not
classify it as a bug from the GTK+ perspective - possibly a feature
request or enhancement request, but not a bug.

Tim



  reply	other threads:[~2011-07-12 23:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 18:45 gtk scroll bar: upstream bug report Glenn Morris
2011-07-10 17:12 ` Jan Djärv
2011-07-11  7:59   ` Andy Wingo
2011-07-11 10:19     ` Jan Djärv
2011-07-11 12:31       ` Richard Riley
2011-07-12  9:04         ` Miles Bader
2011-07-12 15:54           ` Jan Djärv
2011-07-12 23:39             ` Tim Cross [this message]
2011-07-13  5:46               ` David Kastrup
2011-07-13  6:28                 ` Tim Cross
  -- strict thread matches above, loose matches on Subject: below --
2011-07-13 11:30 grischka

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='CAC=50j-fC3eCHnfvbEfZLNJ3dNSdjT+8TG+6ceRp2ChyQ2P9bQ@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=miles@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).