Gitx GitX → 0.7

Comments and changes to this ticket

• 

  Pieter de Bie January 25th, 2009 @ 04:46 PM

  • Milestone set to “0.7”
  • State changed from “new” to “open”

  A "go to current branch" button should be easy to add. I'll put it on the list for 0.7

• 

  Dave Grijalva January 26th, 2009 @ 09:47 PM

  We could also use some clever variant of what the cli version does: "# On branch branch_foo. 2 commits a head of origin"

  On the status bar, we could put the current branch name and, if applicable, the number of commits ahead or behind the tracked remote branch.

• 

  jdwyah January 28th, 2009 @ 05:59 PM

  I'd love it if the current branch were displayed on the commit page as well. It's tough to know where the commit will go.

• 

  Johannes Gilger March 29th, 2009 @ 12:40 AM

  I've created a patch which display the current checked-out branch (i.e. the one HEAD points to and which will receive any commits) in the window-title. It also displays a message if the HEAD is detached.

  It's really hard to find a good spot to put this call, and I'm hoping it will get better once we get refresh-on-change or refresh-on-interval.

  Anyway, the commit is http://github.com/heipei/gitx/co... and as usual it's on my bugfixes branch at http://github.com/heipei/gitx/tr...

• 

  Pieter de Bie March 31st, 2009 @ 02:45 AM

  The patch looks fine, but I think you're right in that it's hard to put this in a good spot. The whole PBGitRepository naming stuff is a bit messy. If you look at the calls GitX makes before actually loading it, you can see quite a few things are duplicated.

  I think it's time to rewrite part of that stuff to make something nicer. I'd rather wait with applying your patch until that is done, to keep things simpler.

• 

  Johannes Gilger March 31st, 2009 @ 10:33 PM

  Well, a general concept would be nice ;) Are we talking a few functions here or a complete rewrite? Is it realistic to keep this in line for 0.7? Or should we just release 0.7 with the intermediate solution, which isn't optimal, and schedule the rewrite for a later release?

• 

  Johannes Gilger May 28th, 2009 @ 01:17 PM

  Hm, since this is included in master/stable now I'd say we could close the ticket (for now), to get closer to our own goal of 0.7.

  Maybe Pieter has an internal "stuff I want to rewrite" list, where he could put this thing.

• 

  Pieter de Bie May 28th, 2009 @ 01:22 PM

  I've got a mental list, but I should get better organized :) I think I
  used to use the TODO wiki page for that, until other's started adding
  stuff to that ;)

  I merged this in by accident, but I found I really like it, so we'll
  just keep it in and see what to do with the mess later. Thanks!

  [state: resolved]

• 

  Pieter de Bie May 28th, 2009 @ 04:31 PM

  • State changed from “open” to “resolved”