From: Pavel Roskin <proski@gnu.org>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: [RFH] QGit: how to cram a patch in a crowded screen
Date: Wed, 30 May 2007 20:23:33 -0400 [thread overview]
Message-ID: <1180571013.3582.32.camel@dv> (raw)
In-Reply-To: <e5bfff550705301118k4ca8720bna260e171f0eb83ca@mail.gmail.com>
On Wed, 2007-05-30 at 21:18 +0300, Marco Costalba wrote:
> My (crazy) idea is:
>
> - Let switch from message to diff content scrolling down after the end
> of message.
...
I'll appreciate if you follow standard conventions for standard GUI
actions and don't change the behavior of such basic keys as arrows.
It would be better to use something more advanced for application
specific behavior. I belong to the post-vi generation, so my mind
cannot easily associate letters (like 'i' and 'k') with up and down
actions. But we could use some key combinations with obvious
"directional meaning", such as Ctrl-arrows.
I've said it before, and it's worth repeating - any key must be
discoverable through the GUI. No key or feature should be discovered by
accident - it would be a sign of bad design.
> So I imagine two labels for each content type:
>
> - for message content a top right label called "Up" and one in bottom
> right position called "Diff"
...
> I plan also to change the labels in something more intuitive with
> scroll action, as example adding an up and down direction little
> arrows next to them.
I'm afraid it would misuse the paradigm of labels. It should be
buttons, perhaps in the toolbar.
> P.S: In case someone wonders what's the goal of this label madness. It
> is to be able to browse a repo in either both sequential directions,
> up or down, using only the mouse wheel.
It may be a cool feature, but users don't expect the mouse wheel to
change anything other than position of the text. Switching the revision
by the scrolling the wheel would be a feature discovered by accident.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-05-31 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 8:46 [RFH] QGit: how to cram a patch in a crowded screen Marco Costalba
2007-05-26 9:34 ` Andy Parkins
2007-05-26 20:44 ` Marco Costalba
2007-05-27 15:38 ` Jan Hudec
2007-05-27 15:56 ` Marco Costalba
2007-05-31 19:56 ` Jan Hudec
2007-06-02 11:37 ` Marco Costalba
2007-06-04 15:41 ` Jan Hudec
2007-05-30 13:08 ` Andy Parkins
2007-05-30 18:18 ` Marco Costalba
2007-05-31 0:23 ` Pavel Roskin [this message]
2007-05-31 4:39 ` Marco Costalba
2007-05-31 9:27 ` Alex Riesen
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=1180571013.3582.32.camel@dv \
--to=proski@gnu.org \
--cc=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).