Visualizing dependencies between LabVIEW classes

[crelf]

I wasn't quite sure which category to post this in: I know guys like Jack and Jon have been looking into some of the visualization capabilities of other languages and how to extend the LabVIEW IDE with them - check out this cool dependency visualization tool Jon put together:
 
http://www.labviewcraftsmen.com/blog/labview-class-dependency-viewer

[MikaelH]

That's a very cool way, this diagram type should be added to the UML standard :-)

[mje]

That's fantastic! Jon seems to have done a great job.

[jon_mcbee]

Hey guys,

 

I updated the tool based on some feedback from John Lokanis, I'd be interested in hearing your feedback, especially on how to host the VIP.  I put the VIP on my blogsite as an experiment to see if I could drive traffic up but I know its not the proper place for it.

 

http://www.labviewcraftsmen.com/blog/labview-class-dependency-viewer-part-2

 

Thanks

Jon

[hooovahh]

I'd be interested in hearing your feedback, especially on how to host the VIP.

You're welcome to do what you want with your contribution to the community, but I generally recommend code be posted in the Code Repository here on LAVA.  This has version tracking, it generates a new thread for submitted code, so user discussion can be linked to the code posted, and a few other benefits like download number tracking, etc.

 

Generally you post it as uncertified then if interest level (and time) permit it is updated to certified.  Here's another link on how to submit code.

 

https://lavag.org/topic/10351-how-to-submit-code-to-the-code-repository/

https://lavag.org/topic/10350-how-does-the-code-repository-work/

[eberaud]

Truly amazing tool. I now have a very visual way to explain the impact of my code refactorization. Jon, where can we find the legend about the colors and shapes for the force diagram and dependency wheel? Also, I originally thought the shape of the leaves on the dependency wheels indicated the direction of the dependency, but it now seems to me that it only depends on the size the libraries takes on the wheel.

Edited March 3, 2016 by Manudelavega

[Stobber]

I originally thought the shape of the leaves on the dependency wheels indicated the direction of the dependency, but it now seems to me that it only depends on the size the libraries takes on the wheel.

 

The pointy end of the ribbon (or "leaf") connects to the dependency.

 

[eberaud]

Thanks. I guess I might have found a particular situation because of nested libraries:

 

 

[Stobber]

That looks like the kind of red flag this graph is intended to show. Find the ribbons without pointy tips and fix your dependency chains so they all have pointy tips again!

 

Edit: Also, a good rule-of-thumb is not to nest libraries (or classes within libraries). It slows the editor down badly and creates dependency hells like the one you have there.

Edited March 3, 2016 by Stobber

[eberaud]

Good to know. I'll un-nest them! 

[thols]

I'm just getting a blank page for the graphs. Anything else that needs to be installed or other requirements?