git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Marco Costalba" <mcostalba@gmail.com>
Subject: Re: [ANNOUNCE] qgit new "smart browsing" feature
Date: Mon, 4 Jun 2007 09:21:54 +0100	[thread overview]
Message-ID: <200706040921.55861.andyparkins@gmail.com> (raw)
In-Reply-To: <e5bfff550706031339v5ffda0a6u6f520f0c7b49f442@mail.gmail.com>

On Sunday 2007 June 03, Marco Costalba wrote:

> Care has been taken to allow the wheel browsing experience to be as
> natural as possible, in particular a way to avoid to switch when user
> just wants to scroll has been implemented. Also, getting a responsive
> scroll and switch command avoiding false positives was not immediate.

I'm really sorry to say it Marco, but it's really disturbing.  You've 
obviously made great efforts to make it useable, but it just isn't.  The 
scroll wheel behaviour being inconsistent is just annoying.  Sometimes 
scrolling works, sometimes it doesn't, sometimes it switches content, 
sometimes it doesn't.  It's obviously based on timeouts for the different 
functions, but that just means that I have no idea what a particular 
operation will do at any given time.

I'm not sure I like the labels with arrows either; and the fonts changing size 
and visibility is inconsistent and discomfiting.

On the plus side - I do like the idea of being able to perform these 
operations; jumping from revision to revision, or from log to patch is nice.  
However, I think it is unwise to invent a new graphical metaphor for an 
operation that already exists - the tabbed widget.  Similarly, the up and 
down are obvious candidates for toolbar buttons - an already established 
visual.

So - I think that the non-standard methods should be dropped (sorry); and be 
replaced with tabs for the patch/log switch and toolbar buttons for the 
up/down.  Also, the scroll-to-switch, while an interesting idea, gives 
unpredictable behaviour and so is uncomfortable to use.

Sorry for being so negative; it's a shame after your obvious hard work.



Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  reply	other threads:[~2007-06-04  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 20:39 [ANNOUNCE] qgit new "smart browsing" feature Marco Costalba
2007-06-04  8:21 ` Andy Parkins [this message]
2007-06-04 11:20   ` Marco Costalba
2007-06-04 12:09     ` Andy Parkins
2007-06-04 16:15       ` Marco Costalba
2007-06-04 19:03         ` Andy Parkins
2007-06-05  5:50           ` Marco Costalba
2007-06-05 18:48           ` Marco Costalba
2007-06-06  8:30             ` Andy Parkins
2007-06-07  5:11               ` Marco Costalba

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=200706040921.55861.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.com \
    /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).