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: Mon, 4 Jun 2007 18:15:48 +0200 [thread overview]
Message-ID: <e5bfff550706040915v3689e8afwb3dffd5d4caf137a@mail.gmail.com> (raw)
In-Reply-To: <200706041309.54279.andyparkins@gmail.com>
On 6/4/07, Andy Parkins <andyparkins@gmail.com> wrote:
> On Monday 2007 June 04, Marco Costalba wrote:
>
> > The tabbed widget is here to stay. I do not plan to remove it. But the
> > tabbed widget is also slower then a well behaved scroll swicth or link
> > clicking.
>
> Ah - I've not explained myself clearly. What I mean is _another_ tab widget,
> instead of the scroll-to-switch. It can't possibly be slower, as it's the
> same amount of work for Qt... So it would look like this (excuse rubbish
> ASCII art):
>
> +-----------------------------+
> | |
> | <rev list here> |
> | |
> | |
> +-----------------------------+
> | Log | Patch | |
> +-----| |---------------+
> | <diff goes here> |
> | |
> +-----------------------------|
>
> At the moment, you have a label in the top left of the text window that is
> mouse-clicked to change mode; I'm suggesting replacing that with a tab widget
> as above where you mouse click to change mode. It's no more operations,
> doesn't include a strange floating label and is a more standard and
> recognisable user interface.
>
> If you still wanted up and down buttons, they could very easily go to the far
> right of the log|patch tabs, similar to the "close" button on the top tabs.
>
>
Andy,
I have to say that I really like your idea!
Now I really don't know what to do! :-)
Probably I will create a new branch called andy_gui where I'll
implement your idea, while continue to refine the current approach. As
example one enanchment I would like to implement is to keep the labels
normally hidden and show the top (bottom) one only when user scrolls
to the top (bottom) boundary of the view so that we could resolve two
issues: knowing when a scrolling action will cause a switch (i.e. only
when the corresponding label is visible) and do not have the arrows
when not needed.
Another enanchment could be to have only one link per label instead of
two and right clicking on it to show a popup menu with available
alternatives.
Of course at the end there will remain only one! The winner will be,
of course, chosen by a democratic polling among us.
Comments?
Thanks
Marco
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.
next prev parent reply other threads:[~2007-06-04 16:16 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 [this message]
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=e5bfff550706040915v3689e8afwb3dffd5d4caf137a@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).