Variance
variancecharts.com
Variance
1–10 of 56 posts
Re: Variance
#2nice. looks to be built on d3.
Re: Variance
#3nice. looks to be built on d3.
Hi, developer lead here.
Variance is not built on D3; we're using some of the scale code, but that's it.
In fact, variance-standalone.min.js is about 10kB smaller compared to current d3.min.js = )
Re: Variance
#4Apologies that this is about form not substance:
I appreciate the clarity of the "What makes Variance unique?" and "Where is Variance not a good fit?" sections. Really useful.
As someone who makes a data analysis tool (with a bit of viz thrown in), that's probably something we could do better.
Re: Variance
#5truly nice looking charts. Wondering, if the colors and other styles built-in or the user has to define them?
Also, seems only IE10+ version is supported, wondering what prevents the library from working on IE9, since (I think) svg is supported on v9 as well.
Re: Variance
#6Apologies that this is about form not substance: I appreciate the clarity of the "What makes Variance unique?" and "Where is Variance not a good fit?" sections. Really useful. As someone who makes a data analysis tool (with a bit of viz thrown in), that's probably something we could do better.
No apology necessary, as there isn't a useful distinction between "form" and "substance" here = )
My dev background is in the Clojure community, where Rich sets a strong tone about the importance of discussing tradeoffs. We outlined those tradeoffs explicitly on the site because that's always what's on the forefront of my mind when making a technical decision. I'm glad you found it helpful.
Re: Variance
#7truly nice looking charts. Wondering, if the colors and other styles built-in or the user has to define them? Also, seems only IE10+ version is supported, wondering what prevents the library from working on IE9, since (I think) svg is supported on v9 as well.
Variance is production-oriented which, for data visualization, requires a ton of the "designer interface" as much as it does from the "developer/analyst interface".
The CSS is broken out into necessary structural bits (where everything is gray, there are no margins, &c.) and then into visual themes. If you aren't a designer, you can just use the stock theme. If you are a designer then you can start from the ground up to build the visual identity that you need.
At no point do you ever have to start throwing `!important` everywhere to override our styling decisions. We intend to release actual SASS/Compass mixins so that you can generate the structural CSS directly in your workflow instead of juggling multiple CSS files and their implicit relationships.
As for IE9, it's all flexbox issues. All of the charts are responsive, and Variance leans on flexbox CSS quite a bit (which IE9 does not support).
Re: Variance
#8really nice
Re: Variance
#9This reminds me a lot of Vega (https://github.com/trifacta/vega), albeit using a HTML/CSS approach as opposed to a JSON one. By default, I'm excited for new ways to approach data visualization, since its a really exciting topic with no clear winners.
I was worried about the hefty price tag until I realized that it was free for non-commercial projects. Will definitely try and play around with it this weekend, as I imagine combining this with basic Python templating could be an even stronger dataviz REPL than mpld3 or vincent.
Re: Variance
#10This reminds me a lot of Vega ( https://github.com/trifacta/vega ), albeit using a HTML/CSS approach as opposed to a JSON one. By default, I'm excited for new ways to approach data visualization, since its a really exciting topic with no clear winners. I was worried about the hefty price tag until I realized that it was free for non-commercial projects. Will definitely try and play around with it this weekend, as I i…
Variance, like Vega, draws a ton from Wilkinson's "Grammar of Graphics". In particular I wanted something like Hadley Wickham's ggplot2 R library, but on the web.
I toyed with the idea of an explicit data format that could be generated by different tools (I talked about this at the 2012 Clojure/conj https://www.youtube.com/watch?v=xyGggdg31mc). Conceptually that route is cleaner.
However, the reality is that any such scheme requires "escape hatches" to drop into the target representation (be it HTML/CSS, Canvas, &c.). We decided it would be best to embrace a single target, HTML+CSS, rather than try to build an abstraction targeting multiple final rendering systems.