Chiasm does configuration diffing and propagates that through the DOM. Much of the functionality of the Chiasm top level library is implemented in React and probably done better.
The main API to Chiasm is setConfig, which is functionally equivalent to the setState method of React. I'd like to investigate whether it might make sense to re-implement Chiasm on top of React.
Since I started this project about a year ago, lots of things have changed in the Web world. I think it's time to re-visit the foundation of Chiasm in light of these new developments, using the current set of Chiasm examples as a guide/tests for what should be possible. There are also other tools that can replace some current Chiasm components - the ChiasmLayout could be implemented using Flexbox, the DataReduction component could be implemented on top of Datalib (which has very solid multidimensional aggregation support). Also, I'd like to take full advantage of the D3 4.0 modules, and try to leverage Rollup and ES6 as well.
I'd like to get a sense - of all of you watching this project in GitHub, would you be interested in an overhaul of Chiasm? Does the project goal of having easily configurable linked visualizations seem relevant to what you're trying to do? The aim of the project is really to make it easier to author interactive visualizations, and I feel like there is still room in this space for better tools.
I'm thinking of launching a Kickstarter campaign so I can invest some serious time into an overhaul of Chiasm in the coming months. Please let me know if you'd be interested in supporting this effort. Thank you.
Chiasm does configuration diffing and propagates that through the DOM. Much of the functionality of the Chiasm top level library is implemented in React and probably done better.
The main API to Chiasm is
setConfig, which is functionally equivalent to thesetStatemethod of React. I'd like to investigate whether it might make sense to re-implement Chiasm on top of React.Since I started this project about a year ago, lots of things have changed in the Web world. I think it's time to re-visit the foundation of Chiasm in light of these new developments, using the current set of Chiasm examples as a guide/tests for what should be possible. There are also other tools that can replace some current Chiasm components - the ChiasmLayout could be implemented using Flexbox, the DataReduction component could be implemented on top of Datalib (which has very solid multidimensional aggregation support). Also, I'd like to take full advantage of the D3 4.0 modules, and try to leverage Rollup and ES6 as well.
I'd like to get a sense - of all of you watching this project in GitHub, would you be interested in an overhaul of Chiasm? Does the project goal of having easily configurable linked visualizations seem relevant to what you're trying to do? The aim of the project is really to make it easier to author interactive visualizations, and I feel like there is still room in this space for better tools.
I'm thinking of launching a Kickstarter campaign so I can invest some serious time into an overhaul of Chiasm in the coming months. Please let me know if you'd be interested in supporting this effort. Thank you.