-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor entire D3 graph #43
Comments
Current plan: create a d3-force graph from scratch. So, we'll be taking the approach of having react render a dumb container element with a ref in it's render() function. Then the entire network of nodes and connections is rendered in that container using just d3 (w/ enter, update, exit methods). We can build interactivity into the d3 rendered graph with event listeners. |
|
Current pausing is choppy. Potential Solution: Use a single transition per message send and pause Other solution: keep current implementation, increase ticks, and optimize the way history is stored |
Using react-d3-graph contains way more functionality than we need, and is adding unnecessary complexity. I believe the best route forward would be to either greatly prune the codebase of react-d3-graph to the basics, create a d3-force graph from scratch, or start extending a much simpler library like https://github.com/uber/react-vis-force.
Think the last choice will be best + easiest
The text was updated successfully, but these errors were encountered: