<p>Thank you!</p>
<p>I feel stupid for posting a question when there is already a stackoverflow answer. But now that I have that, I have all the information I need.</p>
<p>Greets,</p>
<p>Bram<br>
</p>
<div class="gmail_quote">On May 2, 2012 12:49 AM, "Ivan Lazar Miljenovic" <<a href="mailto:ivan.miljenovic@gmail.com">ivan.miljenovic@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2 May 2012 06:15, Bram Neijt <<a href="mailto:bneijt@gmail.com">bneijt@gmail.com</a>> wrote:<br>
> Dear Haskelllers,<br>
><br>
> I've reacently started with Haskell and during the Dutch Hackaton[3],<br>
> I decided to generate graphs of dependencies. I was thinking about<br>
> doing this for Java earlier, and that weekend I decided to write the<br>
> tooling in Haskell.<br>
<br>
Just to be clear, what are you referring to by "dependencies":<br>
<br>
* Package dependencies<br>
<br>
* Inter-module dependencies<br>
<br>
* Call-graph dependencies<br>
<br>
And are you doing this on a per-module or a per-package basis?<br>
<br>
><br>
> I've written two programs: hs2dot[1] and dotimate[2]. The first<br>
> generates a dot file (Graphviz) from all .hs files below the current<br>
> working directory. The second will take one or more dot files and call<br>
> neato (from Graphviz) multiple times to generate frames of neato<br>
> output from one to the next.<br>
><br>
> Trying hs2dot and dotimate on two sequencial commits in the<br>
> cabal/cabal-install/frames directory already gives me a way to complex<br>
> and full graph. See attached.<br>
><br>
> ==> My question is: What dependencies, if any, would be nice to graph,<br>
> and/or which dependencies could I filter out to keep this from<br>
> becoming a mess?<br>
<br>
First of all, consider this list of existing graph-based visualisation<br>
tools for Haskell and see if any have some features you can duplicate:<br>
<a href="http://stackoverflow.com/questions/7427094/generate-diagrams-for-haskell-code" target="_blank">http://stackoverflow.com/questions/7427094/generate-diagrams-for-haskell-code</a><br>
<br>
I know in SourceGraph, my take was to try and do different kinds of<br>
pruning, collapsing, etc. to shrink the information overload down<br>
(however, I haven't touched SourceGraph apart from dependency updates<br>
for quite a while).<br>
<br>
><br>
> Greetings,<br>
><br>
> Bram Neijt<br>
><br>
> [1] <a href="https://gist.github.com/bneijt/hs2dot" target="_blank">https://gist.github.com/bneijt/hs2dot</a><br>
> [2] <a href="https://gist.github.com/bneijt/dotimate" target="_blank">https://gist.github.com/bneijt/dotimate</a><br>
> [3] <a href="http://www.haskell.org/haskellwiki/DHD_UHac#Utrecht_Hackathon" target="_blank">http://www.haskell.org/haskellwiki/DHD_UHac#Utrecht_Hackathon</a><br>
><br>
> _______________________________________________<br>
> Haskell-Cafe mailing list<br>
> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
><br>
<br>
<br>
<br>
--<br>
Ivan Lazar Miljenovic<br>
<a href="mailto:Ivan.Miljenovic@gmail.com">Ivan.Miljenovic@gmail.com</a><br>
<a href="http://IvanMiljenovic.wordpress.com" target="_blank">http://IvanMiljenovic.wordpress.com</a><br>
</blockquote></div>