On Mon, 29 Jan 2007, Theodore Tso wrote:
quoted text
> 
> One approach which might work is where you hover your mouse over a
> line, and it pops up a tiny window with the blame information if the
> mouse remains stationary for more than a second or two.

Yes. I think that's the kind of interface that most people really want.

Of course, almost always, you'd actually want it in your editor of choice, 
and that's not going to happen. But if it looks basically just like a 
normal editor (perhaps with line numbers - that is fairly traditional in 
annotations), that's the basic most spartan interface I can think of. With 
"hover" just causing the extended information for the few lines around the 
mouse to show up (and a "select <n> lines with mouse" for more than just a 
few lines).

quoted text
> Another thing which would be really useful is where the lines that
> have been changed in the last n commits (where n is probably between
> 3-5) are highlighted using different colors.

That would be very natural for the way "git blame --incremental" works, so 
yes, I agree. Not only does it highlight the likely interesting places, 
but it's very much the natural flow for the whole tool.

Ok. Now we just need some sucker^H^H^H^H^H^Henterprising person to 
actually do this ;)

			Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html