git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv2] gitk: Replace "next" and "prev" buttons with down and up arrows.

From
Paul Mackerras <paulus@samba.org>
Date
Jan 22, 2014, 11:04 UTC
Message-ID
<20140122110448.GB7306@iris.ozlabs.ibm.com>
In-Reply-To
<52DE932E.7090008@xiplink.com>
On Tue, Jan 21, 2014 at 10:33:02AM -0500, Marc Branchaud wrote:
Show 14 quoted lines
> On 13-12-18 11:04 AM, Marc Branchaud wrote:
> > Users often find that "next" and "prev" do the opposite of what they
> > expect.  For example, "next" moves to the next match down the list, but
> > that is almost always backwards in time.  Replacing the text with arrows
> > makes it clear where the buttons will take the user.
> 
> Any opinions on this, either way?
> 
> I've grown fond of the down/up arrows.  I find them much clearer than the
> current next/prev buttons.
> 
> My only niggle about this patch is that the buttons are much smaller,
> requiring a bit more precision clicking.  But the smaller buttons allow more
> room for other widgets.

I showed it to a few colleagues who use gitk a lot. One was indifferent, the others liked it, so I have applied it.

Thanks, Paul.

Previous: Marc BranchaudNext: Junio C Hamano
Message 8 of 12 in “gitk next/prev buttons”
  1. Lucas Sandery [three am design]Oct 1, 2013
  2. Lucas SanderyOct 2, 2013
  3. Marc BranchaudOct 8, 2013
  4. Jonathan NiederOct 8, 2013
  5. Marc BranchaudOct 8, 2013
  6. [PATCHv2] gitk: Replace "next" and "prev" buttons with down and up arrows.Marc Branchaud, Dec 18, 2013
  7. Marc BranchaudJan 21, 2014
  8. Paul MackerrasJan 22, 2014
  9. Junio C HamanoJan 22, 2014
  10. Paul MackerrasJan 23, 2014
  11. Junio C HamanoJan 23, 2014
  12. gitk: Rename "next" and "prev" buttons to "older" and "newer".Marc Branchaud, Oct 8, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.