-
Notifications
You must be signed in to change notification settings - Fork 0
Session 2C: Chiasm Project
https://github.com/visfest/topics2015/issues/25
Chiasm Project: an open source initiative to make it easier to declare visualizations with reusable components.
Configuration drives a lot of the parameters that we usually hard-code in d3 examples.
What's the difference between this and projects like Vega and Highcharts?
It is similar in spirit, but the focus of Chiasm is on interaction, linking charts together which is not practical with those projects.
How painful is it to dig in and make something custom? (a lot of packaged frameworks work great for whatever designed purpose, but are hard to force into an unanticipated use case)
Making a Chiasm component is not too difficult, especially if starting from an existing d3 block. You can use other web technologies like Leaflet in this example
What if you find an interesting subset of your data while you are exploring? Can you bookmark that somehow?
One of the goals of the project is to be able to capture the state and put it back into the configuration as a way to accomplish this. Someone mentions using query parameters to accomplish this as well.
Some common ideas between the projects, namely having a definitive state in JSON and updating views based on changes. Need to learn more about React to have more definitive answers.
There is a Chiasm component called links that has a simple domain specific language that can define linking behavior. Look for links: in the config json of this example's index.html
Want to leverage the blocks idea, Chiasm has a boiler plate block that has the bare minimum. There are also lots of examples in blocks as well.