On Monday 2007, June 04, Marco Costalba wrote: > I have to say that I really like your idea! Hurrah! See - even a blind golfer knocks one in eventually :-) > Probably I will create a new branch called andy_gui where I'll > implement your idea, while continue to refine the current approach. Great stuff. If I get a moment, I'll try and chip in with some patches. > As example one enanchment I would like to implement is to keep the > labels normally hidden and show the top (bottom) one only when user > scrolls to the top (bottom) boundary of the view so that we could > resolve two issues: knowing when a scrolling action will cause a > switch (i.e. only when the corresponding label is visible) and do not > have the arrows when not needed. That's certainly an improvement. I think in many cases both labels will be visible - especially in log mode - because most log messages fit completely inside one window. > P.S: Your approach is simple and good, the only downside is the > screen estate taken by the tab bar. But I agree it's absolutly not a > biggie. Yeah, that is a bit of a drawback. How about not putting the tabs on the top or bottom, but on the left or right? In fact if you put them on the right, they'd be almost exactly where your jump labels would be. Maybe this is only better for me, but I tend to have more left-to-right real estate available in the lower half of the screen, primarily because the log messages tend to be limited to 80 columns, but the revision list contains the ever-widening graph. Andy -- Dr Andy Parkins, M Eng (hons), MIET andyparkins@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
