You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this project, it's been very helpful to explore Ruby projects! 🙌
I'm trying to run rubrowser on one fairly large project (8k nodes & 22k edges) which takes a significant amount of time to load and generally difficult to use especially when dragging nodes or when animations run. So I was curious if there was any perspective on how I can be successful with rubrowser in visualizing larger projects?
Some of my initial thoughts:
Maybe there's some low hanging fruit on performance issues in d3, very briefly read that canvas may be more performant
Filtering down some classes on export to avoid loading additional nodes/edges in the browser
Supporting a graph format for a different visualization tool like Gephi
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Thanks for this project, it's been very helpful to explore Ruby projects! 🙌
I'm trying to run rubrowser on one fairly large project (8k nodes & 22k edges) which takes a significant amount of time to load and generally difficult to use especially when dragging nodes or when animations run. So I was curious if there was any perspective on how I can be successful with rubrowser in visualizing larger projects?
Some of my initial thoughts:
Thanks for you input!
Beta Was this translation helpful? Give feedback.
All reactions