That does sound interesting. So the new (student-based) force algorithm would allow for a 'everything is equal' default, or set a certain class of things as more important than others. Or maybe a hierarchy of things a more important (so, classes most important, then packages, then whatever is left over).
I haven't yet personally figured out how I would apply this yet (even the original use), but I am definitely thinking on it. And, yes, if I do find a use, it will probably be outside of software as well. I am really enjoying this toolset known as Moose - both for software analysis, and other business-related analysis. -Chris On Wed, Oct 16, 2013 at 10:12 AM, Alexandre Bergel <alexandre.ber...@me.com>wrote: > >> For example, if you want to connect methods with their defining > classes, and have many classes on screen. It is more important to have a > strong repulsion between the classes, than having the methods of a class > repulsing from methods from another class. > > > > I like the idea, but what do you mean by domain-specific ? > > Do you want to visualize something else than software ? > > The force base layout gives to all the edges and nodes the same value. But > maybe, if you can tell that some nodes are more important than other, then > the complexity can be significantly reduced. > > The algo can be used for anything that is represented as a graph. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >
