Is there a graph of how JUCE’s modules depend on each other? For example:
But maybe up to date and with some classes in the boxes?
Is there a graph of how JUCE’s modules depend on each other? For example:
But maybe up to date and with some classes in the boxes?
You could easily create one yourself using CMake and the GraphViz Option – might need some settings and styling though. But I’m not sure what you mean with
Which classes would you expect to appear in a graph like that, given that some modules probably contain hundreds of classes?
Okay, I’ll have to look into that. I found this quite useful when trying to selectively exclude a module to replace it with a mocked version of a class.
You’re right, including classes definitely wouldn’t work on a static image! I included just the folder names and it became quite large:
I exported an SVG to scroll around in and it’s quite handy, though.