search

anvaka / ngraph

Beautiful Graphs
MIT License
1.41k stars 131 forks source link

How to disable physics simulation? #8

Open mbektimirov opened 10 years ago

mbektimirov commented 10 years ago

Didn't find it in documentation and code. I use ngraph with fabric.

anvaka commented 10 years ago

Could you please tell me a bit more about your use case? Do you already have a graph layout?

mbektimirov commented 10 years ago

I just need a static graph without any random movements. My graph is fully dynamic, nodes are loading on demand.

alexbw commented 8 years ago

+1

gg4u commented 6 years ago

I think that would be helpful possibility to allocate layout computation on selected communities of nodes.

I also load sub-graphs on demand, and actually much of the performance goes to adjust nodes that are not close to the areas a user is looking at.

Typically, the screen area.

I tried to pin nodes that are off the screen area and then free them as soon as they get into the visible are, but the result is not perfect: as soon as they get visible, the edges "rebound" cause all of the sudden forces are applied. And you see things moving around.

So I think that a good approach to test would be to apply forces proportionally to the distance of currently selected node: say, spring-force applied to n-th neighbors is set to 1/n-th, or with a custom function (I play with logaritmic adjustments now).

But don't have coding skill so advanced to modify the library (I am better at designing interaction and UX).

Or even simpler, it may be to turn on and off the layout engine. Now, I found only layout.isNodePinned() as possible solution. I did not found how to set "parameters" to "avoid" force-computation.

Alternatively you can use constant layout and set position programmatically for new layed out nodes - but please share if you find a good logic for expanded-on-demand graphs!!