Ah, excellent design decision! For certain uses, I could definitely see getting away with using the BatikRasterizer. -Toph
On 8/15/06, Brasten Sager <[EMAIL PROTECTED]> wrote:
Unfortunately it does pseudo-require RMagick if you want to render to an image format (PNG, GIF, etc).... which most of the time you probably will. However, if you do intend to use SVG directly, you do not need RMagick. I say pseudo-require because the default rendering logic can easily be overridden if you have some other way you wish to render SVG to an image. The 0.2.0 gem should include a BatikRasterizer class I built for calling Apache Batik to do just that (just by shelling out, nothing fancy). Batik's SVG rendering is much better than ImageMagick's. Unfortunately, it isn't very efficient to fire off a Java process every time you want to render a graph, unless your website gets 2 hits a day or something. But the point is, it's possible, and I'd happily switch the default rasterizer to something other than ImageMagick if anyone has any good ideas in that regard. :) -Brasten On Aug 15, 2006, at 9:43 AM, Topher Cyll wrote: > If it doesn't require RubyMagick/Imagemagick, I am *sold*. =) > > I've wanted to use Gruff for quite some time (both at work and home). > I just couldn't figure out how to get RMagick working with our > (admittedly) strange Linux setup at work, and, despite following the > detailed instructions on the site, couldn't get it working on my Mac > at home either. > > Your screenshots look good! > -Toph > > > > On 8/15/06, Brasten Sager <[EMAIL PROTECTED]> wrote: >> Hey everyone- >> >> I had some downtime this past week, so I put together a graphing >> library I'm calling Scruffy. I would appreciate it if anyone wanted >> to take a look at it and provide some feedback or *constructive* >> criticism. :) >> >> My goal with Scruffy was to create a graphing library that combined >> the great looks (Apple Keynote) and ease of use of Gruff with the SVG >> capabilities of SVG::Graph. Also -- most importantly -- I needed the >> whole thing to be extremely customizable, as my graphing needs seem >> to change from project to project. >> >> As a result, the entire library is fairly well modularized, so you >> can customize most aspects of your graphs non-invasively. Visually, >> everything on the graph is made up of components and layers which can >> also be moved around, removed, customized, etc. >> >> So if anyone wants to check it out and give me thumbs-up/thumbs-down/ >> suggestions either here or at [EMAIL PROTECTED], I would be >> grateful! >> >> RubyForge Site: >> http://scruffy.rubyforge.org >> >> The last three postings on my blog contain information and several >> screenshots: >> http://www.ibrasten.com >> >> Anyway, have at it, thanks in advance! >> >> -Brasten >> >> _______________________________________________ >> PDXRuby mailing list >> [email protected] >> IRC: #pdx.rb on irc.freenode.net >> http://lists.pdxruby.org/mailman/listinfo/pdxruby >> > _______________________________________________ > PDXRuby mailing list > [email protected] > IRC: #pdx.rb on irc.freenode.net > http://lists.pdxruby.org/mailman/listinfo/pdxruby _______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
_______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
