unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gtk scroll bar: upstream bug report
Date: Wed, 13 Jul 2011 16:28:23 +1000	[thread overview]
Message-ID: <CAC=50j9ZLuOmeKVSr6PkbAWAKFGNfxEo3QnV4FoUWOoyM-KL8Q@mail.gmail.com> (raw)
In-Reply-To: <87d3hehgx2.fsf@fencepost.gnu.org>

On Wed, Jul 13, 2011 at 3:46 PM, David Kastrup <dak@gnu.org> wrote:
> Tim Cross <theophilusx@gmail.com> writes:
>
>> On Wed, Jul 13, 2011 at 1:54 AM, Jan Djärv <jan.h.d@swipnet.se> wrote:
>>>
>>> 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.
>>
>> 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.
>
> Consistency may be nice, but not everything is a viewer.
>
> --
> David Kastrup
>

I don't necessarily agree with their views on good UI design or even
their view of consistency. While emacs developers my try to convince
them why different behaviour for a scroll bar would benefit some apps,
at the end of the day, it is up to the GTK+ devs to decide if what we
are arguing represents a bug, a feature request or an enhancement or
just reject it because it does not fit in with their plans/strategy.
The opinions of emacs developers are largely irrelevant - we can try
to argue the case and we can even disagree with their assessment, but
in the end we can only either accept it and move on and continue to
support a build based on GTK+ or reject it and drop support for it.
Anything else is largely irrelevant.

Tim



  reply	other threads:[~2011-07-13  6:28 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
2011-07-13  5:46               ` David Kastrup
2011-07-13  6:28                 ` Tim Cross [this message]
  -- 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=50j9ZLuOmeKVSr6PkbAWAKFGNfxEo3QnV4FoUWOoyM-KL8Q@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=dak@gnu.org \
    --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).