On Fri, May 10, 2002 at 10:46:11AM -0700, Michael A Nachbaur wrote: > On Fri, 10 May 2002 08:32:55 +0200 > Robert <[EMAIL PROTECTED]> wrote: > > > Take a look at Apache::ImageMagick > > In my benchmarks I ran, ImageMagick was way slower than GD. I wrote a > little test, rendering a little text image of 120x30. With ImageMagick, > I was getting 0.3 rps, and under GD with similar circumstances I was > getting 1.5rps. I'm sure I could've optimized the ImageMagick one a bit > further, but that quick test settled it for me. > > I looked at Apache::ImageMagick last night however, and although it > seems pretty usefull, it doesn't really address what I want to do with > my module.
I'm using Imlib2 w/ the c interface (http://freshmeat.net/projects/imlib2perl/) I needed antialias lines, alpha's etc. I modified my app to use a 'dbi' like interface for potentially any media driver. The diferent 'media drivers', gd, imlib2, *pdf/*tex etc all have different ideas how to draw a line, circle, polygon, text, add colors etc. Now all I have to do to use diffent libraries such as Media->new(Driver => 'imlib2'), or Media->new(Driver => 'gd'), Media->new(Driver => 'svg'), Media->new(Driver => 'pdflib') etc. There are may libraries out there, gd, imlib, imlib2, libart, povray, gdk, flash, pdfAPI2, pdflib, tex, latex, svg, imager, imagemagic, ... There are may good reasons to be able to 'just drop in' a driver ... just look at why the unified interface 'DBI' was developed for RDBM's . Ed
