I’ve just uploaded the first beta release of MagickWand for Ruby, my new
binding to ImageMagick. MagickWand for Ruby is a complete rethinking of
RMagick. I call it “RMagick rebooted.”
MagickWand for Ruby objects are managed by Ruby just like any other
object. There is no need for your scripts run GC or call a special
method to destroy them.
This release is the first beta so there’s only 50 or so methods in the
Wand class. I’m planning to add a Pixel class for pixel access and a
Drawing class for 2D drawings but there’s nothing there yet.
MagickWand for Ruby requires a very recent release of ImageMagick,
6.5.0 or later.
If you’re familar with RMagick probably you’ve got some questions.
Is it easier to install than RMagick? No, it’s exactly the same. You
have to install ImageMagick and its delegate libraries just like you do
for RMagick. The MagickWand for Ruby gem does not install any
documentation, though, so it installs faster than RMagick.
Given that we’ve already got RMagick and MiniMagick, do we really
need another binding to ImageMagick? I like to think that MagickWand is
to RMagick what Heath Ledger’s Joker is to Jack Nicholson’s Joker.
Is this the end of RMagick? Absolutely not. I’ve supported RMagick
for over 6 years. I don’t plan on stopping bug fixes or enhancements. In
fact, now that MagickWand is released my next task is a new release of
Everything there is to know about MagickWand for Ruby is at
Report bugs, ask questions, whatever, at the usual locations on
RubyForge [http://rubyforge.org/projects/magickwand/]. If you do try it
out, you’d be doing me a great favor by dropping me a line to say so.
Credits: Thanks to Luis L. for rake-compiler, and Thomas L. for