[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Revision graph revisited

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2006-02-03 16:46:47 CET

I have always seen the Revision graph as a strange beast, but it's
quickly growing into a powerful ally with the changes in the latest


However, the layout of the graph is a complicated matter. We have
already had suggestions on the list to collapse columns, where Steve
replied that it would be hard to do because of their complexity.


I would go as far as to suggest that there are two different cases that
have to be handled when laying out a revision graph. Sometimes it's
highly practical when multiple different paths end up in the same column
(tags for example) and otherwise one would like to keep each unique path
in a unique column (typically with branches). Unique columns would also
facilitate collapsing/folding.


Now the revgraph creates good layout (imho) for graphs showing tags, but
less good for complicated branching or copying. I have attached a word
document containing two takes on a revision history graph for a file
with many copies. (Sorry about the word document, it was the only half
way decent way I could edit the wmf-file... :-/ ) The graph generated by
the revgraph is hard to read and not very suitable for the information
being presented. The modified one contains exactly the same information,
but with each unique path in a separate column. (Columns being generated
left to right where columns are ordered in order of creation.)


I would suggest to either having a way to manually switch how the layout
is done, or (preferably) stack typical tags (with no modifications) in a
single column and let branches (with modifications) have unique columns.


Hope I'm making sense.



To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org

Received on Fri Feb 3 16:51:22 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.