@decentralion, I thought we might want to use a thread here to discuss and coordinate chart design/dev. The goal is to mix the different perspectives/routes to developing the chart to see what we find, then bring it all together so we have a single component for both the App and research. When I have something more technical to offer via a pull request, I’ll do my code write ups there. Hope that sounds right.
Anyhow, we discussed on the call this morning about how we can separate computational components from rendering components (math vs drawing) in anticipation of a React+d3 chart. For example, the
ticked() function that gets called
ontick from the force simulation intends to update the chart via a d3 based calculation. Before we had
d3.selection nodes updated, but we could also have React components updated like this example. So, even though the d3 function is calculating the movement, the function passes the
ontick rendering to a React component not a
I think that reflects the demarcation we discussed that will enable me to continue offering you useful d3 code until I get more up to speed with React.
My work plan entails this:
- extend existing JS into Python Jupyter Notebook for @mzargham, with relevant unit testing on the Python functions
- restructure JS code to separate calcs from rendering while incorporating Hackathon functionality
- SVG rendering unit testing
Questions and suggestions welcomed!