git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: "Andy Parkins" <andyparkins@gmail.com>
Cc: git@vger.kernel.org, "Pavel Roskin" <proski@gnu.org>,
	"Jan Hudec" <bulb@ucw.cz>
Subject: Re: [ANNOUNCE] qgit new "smart browsing" feature
Date: Tue, 5 Jun 2007 07:50:53 +0200	[thread overview]
Message-ID: <e5bfff550706042250q6f4034d0y15c65516375fcf4a@mail.gmail.com> (raw)
In-Reply-To: <200706042004.01819.andyparkins@gmail.com>

On 6/4/07, Andy Parkins <andyparkins@gmail.com> wrote:
> On Monday 2007, June 04, Marco Costalba wrote:
>
> > P.S: Your approach is simple and good, the only downside is the
> > screen estate taken by the tab bar. But I agree it's absolutly not a
> > biggie.
>
> Yeah, that is a bit of a drawback.  How about not putting the tabs on
> the top or bottom, but on the left or right?  In fact if you put them
> on the right, they'd be almost exactly where your jump labels would be.
>

Andy, another point scored for you!

I will do exactly that!


Now the only drawback it remains (more "mental" then real) is that the
user already scrolls down to read the message / patch and, at the end,
it's easier to just continue scrolling to jump to next/previous
revision then move the mouse to point the tab, click, and go back to
start scrolling again: a finger against a double hand movment + click.

Yes, I know, I'm veeery lazy ;-)


Marco

  reply	other threads:[~2007-06-05  5:51 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
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 [this message]
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=e5bfff550706042250q6f4034d0y15c65516375fcf4a@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=andyparkins@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=proski@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.
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).