However, SVG seems to be the way to express vector graphics, so my immidiate reaction (this feels a bit like /. karmawhoring) was "how does SVG fit into all this?"
SVG would be a great way to generate graphs, but there are several problems I have right now:
a) hardly any browsers have SVG support;
b) there aren't any (last I checked) SVG->Bitmap serializers for Perl;
c) there's an SVG->Bitmap serializer for AxKit that recently was announced, but it's ImageMagik-based (bad mojo, IMHO);
d) even if all the above weren't true, I haven't seen any mature XML->SVG stylesheets that can render pretty pie/line/bar charts.
I hope that doesn't sound like a rant. I have a warm and fuzzy place in my heart for pretty graphs (I'd *really* like to use OpenGL, but...*shrug*). However, I have real-world requirements for a client's project right now, and instead of building a Perl interface to librsvg (which I might do eventually), I'd rather use something that works and is a known quantity.
GD::Graph doesn't output SVG, does it? Then, I thought that for portability (at least) when expressing graphics in XML it would be nice to express it in SVG. But OTOH, SVG for input make perhaps little sense in this case because is SVG too low-level for this purpose?
GD::Graph is bitmap based. It's a pretty cool/convenient package, if somewhat limited (with a few minor bugs).
--man Michael A Nachbaur <[EMAIL PROTECTED]>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
