Changes between Version 5 and Version 6 of VisualizingDjangoChangesetDependencies

Timestamp:

May 11, 2007, 11:42:23 AM (17 years ago)

Author:

Ramiro Morales

Comment:

--

VisualizingDjangoChangesetDependencies

@@ -7 +7 @@
 Later the cause became evident: The ''C'' changeset wasn't being considered by {{{darcs}}} because I had previously answered "no" when it offered me to apply a (chronologically previous) changeset ''B'' on which ''C'' depends (dependency in this context means both ''B'' and ''C'' modify some overlaping section of some file).
 
-Given the fact that in {{{darcs}}} patches (changesets, patchsets) are first class citizens, it is relatively easy (when compared with other revision control systems) to track and visualize the dependencies among them by using it together with some related '''![3]'''tools and '''![4]'''{{{GraphViz}}}.
+Given the fact that in {{{darcs}}} patches (changesets, patchsets) are first class citizens, it is relatively easy (when compared with other revision control systems) to track and visualize the dependencies among them by using it together with some related '''![3]'''tools and '''![4]'''{{{Graphviz}}}.
 
 If we add a couple of ad-hoc scripts and some tips from the experience gained to the mix we can get something like this (partial output):
@@ -94 +94 @@
 Finally, we feed the result to {{{dot(1)}}} (also part of {{{Graphviz}}}) to get our final output. For some output methods (PDF [via Postscript], server/client side image maps) we'll be able to click on the nodes and get our Web browser to go to the Django Trac page associated with the changeset at hand.
 
-For the PDF output we use {{{poster(1)}}} on the intermediate Postcript output to create a legible non-cropped multi-page output.
+For the PDF output we use {{{poster(1)}}} on the intermediate Postscript output to create a legible non-cropped multi-page output.
 
 == Files ==
@@ -115 +115 @@
 
  * The "Tailorization" node represents an initial synthetic patch created by {{{darcs}}} from which every other leaf node depends on, perhaps it would be better to find a way to eliminate it from the graph.
- * I attempted without success modifying the {{{darcs-deps}}} script to eliminate the nodes that have no other nodes depending on them, next try will be using {{{Graphviz}}}'s {{{gvpr(1)}}}.
+ * I attempted without success modifying the {{{darcs-deps}}} script to eliminate the nodes that have no other nodes depending on them, next try will be using {{{Graphviz}}}'s {{{gvpr(1)}}} tool.
+ * The PDF output for this iteration has some problems, something that didn't happen before; it seems there is some non-deterministic interaction between {{{poster}}} and the {{{dot}}} PS output we feed to it. It would be nice to be able to create multi-page output  directly from {{{dot}}}, ideas welcome.
 
 == References ==