Live data from Hacker News

Polychart.js: An Interactive Charting Library

polychartjs.com

51–60 of 72 posts

Re: Polychart.js: An Interactive Charting Library

#51
post #22

This uses Raphael. Which is awesome. Alternatives to Raphael is d3. Alternatives all together is NVD3. If you haven't seen this one, go check it out.

Agrees with you that Raphael is very awesome. A difference between Polychart.js and NVD3 is its flexibility: the way one can overlay charts, or even plot any change in polar coordinates. (We took a lot of ideas from R and ggplot2, something data scientists use). We share your love with d3 also, which unfortunately will not ever work in IE. So until the rest of the world catches up... ;)

Why wouldn't it work in IE?

Re: Polychart.js: An Interactive Charting Library

#52
I currently develop a powerful JavaScript diagramming library (very different capabilities than charting), and charge more than this, though its done per domain and not per developer, with exceptions for OEM customers who need to deploy it everywhere. I'd recommend you go that route instead, most of our customers seem very happy with the model.

The charting space by contrast seems significantly bloated to me. This library may well be awesome, but I'd recommend you explain within my first minute or two on the page why this is better than the host of free options out there.

Re: Polychart.js: An Interactive Charting Library

#53

I currently develop a powerful JavaScript diagramming library (very different capabilities than charting), and charge more than this, though its done per domain and not per developer, with exceptions for OEM customers who need to deploy it everywhere. I'd recommend you go that route instead, most of our customers seem very happy with the model. The charting space by contrast seems significantly bloated to me. This li…

The fact that you can pay for it is a competitive advantage for megacorps.

Re: Polychart.js: An Interactive Charting Library

#55
post #22

Earlier quoted context omitted.

Agrees with you that Raphael is very awesome. A difference between Polychart.js and NVD3 is its flexibility: the way one can overlay charts, or even plot any change in polar coordinates. (We took a lot of ideas from R and ggplot2, something data scientists use). We share your love with d3 also, which unfortunately will not ever work in IE. So until the rest of the world catches up... ;)

Why wouldn't it work in IE?

d3 produces SVG graphics, which aren't supposed by versions earlier than IE 9.

There are ways to turn d3's SVG output into a canvas element. Those earlier version of IE also support VML, but I don't recall any quick ways of doing from d3 output to VML off the top of my head.

Re: Polychart.js: An Interactive Charting Library

#56
False. You do not support basic guides like highcharts, you are not the most intuitive and interactive for the browser... yet.

It seems like this feature is the most overlooked, and it is one of their strongest selling points. As you mouse along the chart regardless of your y axis it has guides that will show the datapoint tooltip information closest to your x axis if you have a line selected or have mouseover'd a line.

Your charting library is however well thought out, there are a few features that I would be interested in seeing from morris.js and rickshaw.

Re: Polychart.js: An Interactive Charting Library

#57

Earlier quoted context omitted.

It's hard to evaluate when the projects are so new. It was a similar problem with Crossfilter/Datavore/Data.js/Miso Dataset when they all came out. If I had to pick, I'd go with Vega because I think it has the most potential to develop a community around it. Especially as a bridge between Python/R and D3.js through JSON. Think iPython notebooks, R Shiny, etc.

Perhaps this is not the right place but can you expand on the Crossfilter/Datavore/Data.js/Miso Dataset comment?

They are all libraries for managing datasets with fast or convenient filtering. Useful for linking visualizations together through a common data model.

None have become as popular as d3.js though, so it's still hard to compare them.

Re: Polychart.js: An Interactive Charting Library

#60
post #19

I like the interaction layer (at least the way it's described). The per-developer pricing for this is really strange though. If I implement this in an app, it may start out as my app, and then other developers may collaborate later on, sometimes temporarily. How much would this cost? I have no idea, so I'd probably skip it entirely for any project.

Thanks JangoSteve for the feedback. Would a per application or per domain licensing be something you'd be looking for?

Yes. Per application (or domain, it'd be hard to make a technical distinction anyway) would make more sense I think for typical use cases.
Post reply on HN