On Tue, Jan 5, 2016 at 9:57 AM, smaug <sm...@welho.com> wrote: >> I really liked a lot about the blame implementation that bonsai had, >> unfortunately we don't have a running copy any more AFAIK so it's hard to >> take a >> look at it. >> >> For one thing instead of showing author and changeset (or version in CVS) >> for every line, it grouped subsequent lines changed at once together and >> showed that information only once for them. >> For the other, when you moved your mouse over that author/changeset >> "blame" info, it didn't just show a tooltip but a full-fledged HTML box >> where e.g. >> bug numbers in the checkin comments could be linked and you could call up >> that link (in a new tab probably) right away and directly go to read the bug >> that changed this code. > > Indeed, bonsai had the best blame UI I've ever used, tough even that could > have used some ux help. But at least it was efficient. > Comparing to ViewVC for example Bonsai needed 1 click vs ViewVC's 6 to get > to the relevant bug. > https://bugzilla.mozilla.org/show_bug.cgi?id=1200362#c5 > hg annotate takes 3 clicks. > Since each click means a page load, optimizing that would be great.
I generally agree. Especially about Bonsai, though far from perfect, being the best UI I've personally used. Though I'd be careful to simply measure number of clicks. Bonsai required a lot of swooping and hovering, which also adds to the effort of reaching information. For example, clicks which display information in-page can be made a lot faster than ones that navigate, so that might be an option to consider as well. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
