git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Steffen Prohaska <prohaska@zib.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, git@vger.kernel.org
Subject: Re: [PATCH] user-manual: mention git gui citool (commit, amend)
Date: Thu, 2 Aug 2007 23:01:01 -0400	[thread overview]
Message-ID: <20070803030101.GI20052@spearce.org> (raw)
In-Reply-To: <107BD473-E055-47D0-9720-9D878BDAB954@zib.de>

Steffen Prohaska <prohaska@zib.de> wrote:
> Maybe, this would be sufficient. I mentioned the pop-up explicitly
> because it wasn't obvious to me right away. The reason might be that
> my brain adjusted too much to the Mac I'm using. Right-clicking and
> pop-ups are rarely used on Macs as the only access point to essential
> features, such as selectively staging diff hunks. Typically an icon
> or menu entry guides you explicitly to every feature. Pop-ups are only
> used for 'optimized' access but never as the only access point.

Steffen, you seem to be more in-tune with the Mac UI standards
than I am.  Any suggestions on what I can do in git-gui to make
this feature more obvious to users?

I myself use a Mac OS X based PowerBook as my primary development
system, but I have to admit, I'm not the best GUI developer that has
ever walked on this planet.  Far far far from it.  I get by, if that.
The fact that git-gui is even usable by mortals is a minor miracle.

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.


Side note: Someone recently asked me how to move individual files
to the left side of the UI (to stage them).  Apparently this person
had been using git-gui for months by just clicking "Add Existing"
(recently renamed to "Stage Changed").  It never occurred to the
user to try clicking the file's individual icons.  Or to select
the files they were interested in and look for a menu option that
might work on that selection.

-- 
Shawn.

  parent reply	other threads:[~2007-08-03  3:01 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     ` Shawn O. Pearce [this message]
2007-08-03 12:56       ` [PATCH] " J. Bruce Fields
2007-08-04  6:33         ` Shawn O. Pearce
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=20070803030101.GI20052@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).