Hi, really great ideas here and I'm looking forward for these new goals. I just wrote my own deptree-plugin to generate a tree graph with all project dependencies. When starting this work I was also looking for the right place to implement such a feature but didn't found the right place - now I know ;-) I also had problems to extract the right information and with the different scopes but I hope the new goals will help.
My plugin generates a *.dot [1] file for all dependencies and uses the DOT tool from [2] to generate a SVG image from it. Looks really cool! By using SVG you can link subgraphs to other SVG images. This enables you to navigate through a deptree like clicking through a web site ;-) I tried to attach a sample but it was to large. [1] http://www.graphviz.org/cgi-bin/man?dot [2] http://www.graphviz.org/ - Fabian Jörg Schaible schrieb: > Brian E. Fox wrote on Thursday, January 18, 2007 3:34 PM: > >>> This is true, I haven't used dependency:resolve until you >> mentioned it. >> I >>> guess the only difference is that it doesn't show the scope of the >>> dependencies, but this could be easily resolved. >> Heh, actually I just added that feature last night before reading >> this thread. (mdep-57). > > Really cool :D > > - Jörg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
