this issue is for the purpose of settling on a final charting solution for this module, as it will be the one we use with sampler api to generate all of our metrics sparklines for the redesign.
options:
- third party solution, currently google chart api. over at #428680: Change usage stats to not use google charts it's been taking some heat for being a black box solution, which we try to avoid on drupal.org.
- in house solutions
- client-side, like flot module. this will reduce the usage of our server resources, but would not work in all cases as the client has to support whatever we're using. flot uses javascript, which is pretty ubiquitous in the 2010 browser world
- server-side, probably some kind of system where we generate sparkline images, cache them, and send them over the wire. would eliminate client-side inconsistencies, but would put more burden on our processor power, storage, and bandwith.
i vote for b.1.
i'd like to get this resolved asap, as our goal is to have some metrics go live for the next sprint demo.
Comments
Comment #1
drummI'm okay with b.1. too. Flot has come up a couple times before, so it should be good.
Comment #2
drummComment #3
dwwI don't have a strong preference. I have a mild preference to use open source, not google. But, existing and working code is better than a pristine design/plan. ;) If it's going to take more than 1 hour to convert from google charts to flot, I'm not sure it's worth it (at least not right now). We can always revisit this later -- if/when it becomes a problem. I'm more concerned about getting some metrics up and sparklines placed than I am about the potential evil of Google-the-black-box.
Comment #4
drummAgreed with dww. Previously it was said this won't tkae long, but the 1hr limit is good.
Comment #5
dwwmikey_p converted this module to use flot: http://drupal.org/cvs?commit=423792
Comment #6
dww(better title for posterity)