On Fri, Mar 19, 2010 at 12:41 AM, Nathan Kinsinger <[email protected]> wrote: > > On Mar 18, 2010, at 3:14 AM, Pieter de Bie wrote: > >>> I think the scope bar (the blue one) should stay as is (though the color >>> doesn't). All the others I'd be willing to change if someone has a better >>> idea for how to organize them. >> >> I don't get the scrollbar. It's something of a mix of specifying rev >> parameters and the branch menu on the left. Now you suddenly have two >> different ways to select a branch -- choose one in the sidebar, or >> choose something else in the scope bar. Why? How will you ever make >> this clear to users? > > > The scope bar filters which commits are shown in the tableview. Branch > selection in the source view moves the tableview to that branch's commit. > > Scope bars are quite common, here is an example from the Finder: > <http://brotherbard.com/gitx/scopebar_screenshot.png>
I know scope bars are quite common, but I think they're not used correctly in this situation. > I should note that I am not using rev parameters to do this, I am filtering > the commits themselves. I have GitX store all the commits and just re-filter > them when the selection changes so it doesn't have to go out to git just to > change the view. In some cases it has to re-graph the commits, but I still do > that with the commits in memory. Before each selection change I check to see > if any of the refs changed and only reload the commits if they did. I'm still confused. I don't understand what it does. If you selcet 'experimental' on the left, and 'All' in the scope bar, what does it display? Does it display all branches? That's not really filtering, is it? It's more like expanding the search. Does the sidebar influence anything once you select 'all' or 'local'? If not, then why is the scope bar 'within' the detail view of the branch list? - Pieter To unsubscribe from this group, send email to gitx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
