Custom Charts w/ Perl and GD
An anonymous reader writes "This article describes techniques you can use to create new levels of usefulness in your dynamically generated charts with Perl and GD. Cook up some automatically generated graphs for your organizational meetings or live enterprise directory data. Annotate the charts with readable text that delivers more information than the standard pie chart. Using the power of GD and Perl, you can link various data and images together to create sophisticated charts that will help bring visual interest to your applications."
Heh. Congrats on being modded 'interesting' for that.
Any chance I can get funny moderation? Or insightful, maybe?
The code is out there. Whenever the graphics folks want to start contributing, they can.
I can throw myself at the ground, and miss.
Remember how programmers always talk about using the right tool for the right job?
If you want to do something like graphing, then why not learn a language like R, where you can easily and interactively create amazing visuals in very little time? I write code in Java, python, bash, and interact with Oracle and MySQL database. R fits in as a nice way to visualize data, and it's very easy to script up solutions that you can plug into your programming pipeline.
Check out http://addictedtor.free.fr/graphiques/index.php for examples (with source code)
I make my PHP scripts output SVG. I feed it to ImageMagick's "convert", and then outputs it to the user.
I agree with what you're saying, but I think you've got the onus wrong. As someone with design and coding experience, I can say that FOSS programmers often bend over backwards to package things nicely, but are often rebuffed by non-programmers if the interface is not 100% to their liking.
There is a disconnect, but IME it comes from people who think that being a user entitles them to sit back and wait for manna to drop from heaven. The bottom line is simply this: If you're going to work in FOSS, then you have to get your hands dirty. This almost necessarily means learning a little about areas that are not your forte. In order for there to be reasonable cooperation, we need to speak the same language. In the Perl community especially, there is a real desire to learn new things and share knowledge, but if designers et alia aren't willing to learn at least a little Perl, then there's not much to be done.
"Don't make me look at code" is, unfortunately, not often a valid condition for any FOSS participant, regardless of their other talents.
Crumb's Corollary: Never bring a knife to a bun fight.
That's the stupidest comment that gets repeated about all sorts of things in Open Source. There are people who can document, who can theorize and who can draw much better than they can code. If coders and those who can't code but have potential for contribution would communicate, we'd end up with better software. Software isn't just code, sorry to say. Yes yes, "show me the code" is a great line, and wrong for almost everything outside libraries and kernel space (and even then, some documentation writers, theorists and idea people should be involved more than they are by the coders).
- Michael T. Babcock (Yes, I blog)
Judging by the examples, this brings the readability of Perl into graphs.
i echart/warning.en.html
I think I can hear Edward Tufte weeping...
And the only chart they implement is the pie chart:
http://www.usf.uni-osnabrueck.de/~breiter/tools/p
Xix.
"Everything is adjustable, provided you have the right tools"