From: "Shawn O. Pearce" <spearce@spearce.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Steffen Prohaska <prohaska@zib.de>, git@vger.kernel.org
Subject: Re: [PATCH] user-manual: mention git gui citool (commit, amend)
Date: Sat, 4 Aug 2007 02:33:53 -0400 [thread overview]
Message-ID: <20070804063353.GR20052@spearce.org> (raw)
In-Reply-To: <20070803125601.GA28323@fieldses.org>
"J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Thu, Aug 02, 2007 at 11:01:01PM -0400, Shawn O. Pearce wrote:
> > So I'd really love to do better. But frankly I'm at a loss here
> > and just don't know what sort of change to make.
>
> The one thing that struck me when I fired up git-gui was that it wasn't
> obvious to me which things I should try clicking on.
Yea, that I have noticed with other newbies. I have recently had
the chance to observe a few new users work with git-gui for the
first time and I have noticed that they just don't quite know what
to poke at and experiment with. Unlike with many other applications
where its more obvious what's there for the poking...
> For example: the buttons, drop-down menus, and check-boxes all cry out
> to be played with. But the filenames in the lists at the top are less
> obvious, and it might never have occurred to me on my own to right-click
> on the diff hunks at the bottom. That just looks like passive colorized
> text to me.
It doesn't just look like colored text to me anymore. Which is a
huge problem for me as an interface designer. I know what's there.
BTW, the reason why there's a context menu in the diff viewer?
I right clicked in there one day and nothing happened. The fact
that nothing happen surprised the hell out of me. Even though I
had written all of that code myself. So I went off and added
that context menu.
Later I realized I wanted to just stage that hunk. I could click
on it all I want, but the $@!*@(!@* computer didn't do what I really
wanted it to. So stage hunk was born and added to the context menu.
That experience is actually true of much of the git-gui UI. Things
happen there only because I've actually tried to do something,
only to shock myself when I find out it doesn't work! I promptly
write the patch and contribute it. :)
> I don't know what sort of user-interface conventions say "play with
> me!", though. Random ideas:
>
> - maybe the cursor should change shape over the diff hunks (or
> just the headers?)
That's actually a pretty cool idea. I might play with it just to
see how I feel about the cursor changing and if it gives me any
ideas about what might happen under it. Though as I write this
email I'm thinking that if the cursor changed shape when it was
over the diff hunk header I'd try to left-click the hunk header to
get a reaction from the computer.
> - maybe buttons, hunk headers, file names, etc., should all be
> in the same color?
> - maybe the hunk headers could benefit from a little more
> decoration? I don't know how to do that without just making
> the display look more cluttered, though.
> - maybe left-clicking on diff hunks should do something too?
I just had a thought of putting an actual button icon in the first
column of the hunk header lines. If it looks enough like a button
icon thingy, users might just click on it. And when they do we
can present that diff pane context menu, and look, they can stage
their hunks! ;-)
Just a thought. Utterly random too. Musta been that alpha particle
slamming into a neuron.
Thanks for the ideas. Its certainly given me some things to
experiment with in the next week or so when I can find the time.
--
Shawn.
next prev parent reply other threads:[~2007-08-04 6:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 16:11 [PATCH] user-manual: mention git gui citool (commit, amend) Steffen Prohaska
2007-07-31 0:24 ` Shawn O. Pearce
2007-08-02 18:18 ` J. Bruce Fields
2007-08-02 22:24 ` Steffen Prohaska
2007-08-02 22:31 ` J. Bruce Fields
2007-08-03 5:08 ` Steffen Prohaska
2007-08-03 12:56 ` J. Bruce Fields
2007-08-05 12:59 ` [PATCH v2] " Steffen Prohaska
2007-08-05 13:58 ` Johannes Schindelin
2007-08-05 14:17 ` Steffen Prohaska
2007-08-05 14:48 ` Johannes Schindelin
2007-08-05 15:03 ` David Kastrup
2007-08-05 19:47 ` Steffen Prohaska
2007-08-06 0:22 ` Johannes Schindelin
2007-08-06 5:20 ` Steffen Prohaska
2007-08-06 9:36 ` Steven Grimm
2007-08-06 11:51 ` Johannes Schindelin
2007-08-05 22:22 ` J. Bruce Fields
2007-08-05 22:25 ` J. Bruce Fields
2007-08-06 0:26 ` Johannes Schindelin
2007-08-06 3:51 ` J. Bruce Fields
2007-08-06 19:36 ` Robin Rosenberg
2007-08-06 19:43 ` J. Bruce Fields
2007-08-03 3:01 ` [PATCH] " Shawn O. Pearce
2007-08-03 12:56 ` J. Bruce Fields
2007-08-04 6:33 ` Shawn O. Pearce [this message]
2007-08-05 12:09 ` Steffen Prohaska
2007-08-03 0:05 ` Junio C Hamano
2007-08-03 3:04 ` Shawn O. Pearce
2007-08-03 12:58 ` J. Bruce Fields
2007-08-04 6:20 ` Shawn O. Pearce
2007-08-04 7:44 ` David Kastrup
2007-08-04 14:35 ` J. Bruce Fields
2007-08-05 12:26 ` Steffen Prohaska
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 3:33 Brett Schwarz
2007-08-06 4:06 ` Shawn O. Pearce
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=20070804063353.GR20052@spearce.org \
--to=spearce@spearce.org \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
/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).