<< How Effective is the Mozilla Stability Program? | The roads I take... | Hacking Day And Linuxwochen >>

Finding an Openly Licensed JS Graph Library

As I mentioned at the end of the recent post on stability graphs, I was looking for doing JS-based, dynamic versions of those graphs. Those would be able to always have current data without manually copying stuff around (as I've done previously) and should be available to more people in the Mozilla community.

That said, even though I tried previously to do some canvas magic to create graphs in JS, it's tedious to create all that code by oneself, so I set out to find a library that can help me.

My set of ideal requirements was:
So, I went on a web search and tried to find libraries that would fulfill my requirements. Interestingly, I saw a number of commercially licensed JS libraries floating around, I guess there's some business in creating graphs out there.
The list below is the libraries I took a closer look at (before you ask, flot is not on the list because it requires jQuery and therefore violates my "graphs only" and "lightweight" goals right away):
So none of those turned out to be completely ideal in the light of my goals/preferences. That said, dygraphs looked decent enough so I went with that in the end and have dynamic versions of my graphs implemented.
(Ping me on IRC if you want a link, I don't want to link them on the blog as the uninformed could come to wrong or hasty conclusions looking at the data).

Of course, if you are looking for a graphs library for your project, you might chose completely differently, but maybe the list is helpful to find what fits your needs. ;-)

Entry written by KaiRo and posted on May 1st, 2014 01:12 | 6 comments | TrackBack

Comments

AuthorEntry

Gervase Markham

quote
OFlotcharts?
2014-05-01 13:12

KaiRo

Webmaster

quote
OGerv, as I mentioned right before starting into the list, it's coupled to jQuery and therefore violates my goals.
2014-05-01 13:51

Pete

quote
OWhy lightweight?
Is your app so time and memory critical that you have to save each byte and ms of CPU time? I mean, consider all these frameworks out there as a black box. When they do what you want, fine. Don't care about the rest.

I would agree when it comes to integral parts of an app, like jQuery. The problem there is, once you use it, you can't simply replace it. But a chart library only has a few API calls.
2014-05-01 20:54

KaiRo

Webmaster

quote
OI want to understand as much of the code I write, and I do not want 95% of the pageload be loading libraries. I'm not doing any app there (all my apps have 0 libraries), this is just a page that consists of one big graph.
2014-05-02 13:07

philipp

quote
2014-12-11 23:42

KaiRo

Webmaster

quote
O
Unfortunately, that seems to require D3 and therefore pulls in all that other stuff I don't want.
2014-12-14 16:00

Add comment