On Mar 19, 2:52 pm, Nathan Kinsinger <[email protected]> wrote: > On Mar 19, 2010, at 3:07 AM, Pieter de Bie wrote: > > > 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? > > http://brotherbard.com/gitx/GitX.zip > > Well yes, 'All' does mean everything. It means filter=none. > > In GitX 0.7.x the 'All branches' and 'Local branches' items are treated like > they are individual branches even though they are not. When you select them > the list scrolls to the top and you then need to scroll down to view the > branch you were trying to look at. If you want to go back and forth looking > at just the commits for a branch and all the commits (to see the history as > it relates to other branches) it involves a lot of scrolling. > > The filter UI allows you to select a branch and then go back and forth seeing > the history of just the branch and the history of the project (but still at > the branch). > > Is there anyone else who finds it confusing? Either from viewing the > screenshot or from using it?
Ah! I think. I did not get it at first but it actually is the thing I always thought GitX was missing. (That is, after some cleanup and rethought, because some parts don’t actually wort together well.) So, you’d have your filters on top and on the left side there are your bookmarks. Just like #anchors in html. I too had always experienced the problem that I’d like to see all branches in the view but need to scroll down a little to where my current working branch is. But I understand Pieter’s concerns. You could approach the problem in two ways, I think. One is having the filter act on the sidebar as well, which is I think what you’d expect after having used GitX for a while. This would mean that you’d have the old drop-down filter in the menu bar and the sidebar would only show those anchors which are actually reachable by that view. (All other anchors might vanish or be greyed out.) But the other way is what you implemented, e.g. with the sidebar as a first step. You’d move the view by selecting the anchor and afterwards, you can choose from the filter which branches you want to hide. I think both is valid; the anchor-first solution which you implemented would have the advantage (?) that there are less options possible and that it is therefore arguably easier to use it. (On the other hand, it is not possible to set the filter on branch A and then move the anchor to some earlier branch B as this would then also filter on B. This can be a pro or a con.) The filter-first solution is more in the style of the current GitX but with added anchors. And whereas the other situation gives to few possible combinations, this one will give too many. (Btw. Do you think that the tags in the sidebar should be ordered with the newest on top maybe? This should prevent too much scrolling when you have 10+ tags.) To unsubscribe from this group, send email to gitx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
