[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

[ANN] MagickWand for Ruby 0.1.0

Tim Hunter

6/2/2009 1:35:00 AM

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.

1. 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.

2. 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.

3. 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
RMagick.

Everything there is to know about MagickWand for Ruby is at
http://magickwand.rub....

Report bugs, ask questions, whatever, at the usual locations on
RubyForge [http://rubyforge.org/projects/m...]. 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 Lavena for rake-compiler, and Thomas Leitner for
webgen.




--
MagickWand for Ruby - http://magickwand.rub.../



7 Answers

Marc Heiler

6/2/2009 1:51:00 AM

0

Why was MagickWand created?

I mean quite obviously you must think that MagickWand will be better
than the older RMagick interface, I am just curious what has motivated
you. I looked at the website but I did not find this information. :)
--
Posted via http://www.ruby-....

Tim Hunter

6/2/2009 9:44:00 PM

0

Marc Heiler wrote:
> Why was MagickWand created?
>
> I mean quite obviously you must think that MagickWand will be better
> than the older RMagick interface, I am just curious what has motivated
> you. I looked at the website but I did not find this information. :)

Well, I didn't think that my "motivation" would make any difference to
people who are checking out MagickWand for Ruby. But since you
asked...Who doesn't want a do-over? ImageMagick development is in a lull
and that gives me time to work on a new project. I can't change the
things I don't like about RMagick because that would break existing
code, so I'm taking the opportunity to write an entirely new library.

Compare MagickWand for Ruby to RMagick. The things that are different in
MagickWand are the things I don't like about RMagick. The things that
are the same are the things I do like.

Also there are some differences that affect only me. I think the code
for MagickWand for Ruby will be easier to maintain. The RMagick doc,
which I maintain by hand, is a pain to keep up, so the MagickWand for
Ruby doc is automatically generated by webgen.

--
MagickWand for Ruby - http://magickwand.ruby...

lrupertus

2/17/2011 9:34:00 PM

0

> Still within the 4k rom limit, but will be close to exceeding it after
> adding the attract mode in.
>
> -scott CARGPB#29

Adding more ROM is easy enough but I assume you want to avoid that
making it easier for others to just drop in the new code without
modification? Of course, a lot of -17s are going to be strapped for
9316 out of the box anyway so that might not be as much of an issue
(modification required either way).

I'm looking forward to seeing this one plays out. I just might not
sell my Night Rider after all ;)

seymour-shabow

2/17/2011 9:38:00 PM

0

Gott Lieb? wrote:
> How is 21 going to work, if you disable the credit button, as
> mentioned previously? What about adding center drains? It should be
> easy, just add an exception to the left and right drains. I would be
> curious how many balls go down the middle versus the outlanes.
>

Well, I'd have to add a timer function to determine if the center drain
was just a center drain or if it was a drain after the left and right
drains..... the outhole switch trips in all drain cases ;) I guess I
can make it do the math, SDTM drains=all outhole drains - left drains -
right drains. One way needs math the timer way need finesse.

I probably won't disable the credit button except for the tournament
mode setting, which I haven't decided on 100% yet.

Gott Lieb?

2/17/2011 10:03:00 PM

0

I just figured it would be something like:

switch closure before outhole switch closure <> left drain OR right
drain

I'll stick to high level programming. :-)

Jim

On Feb 17, 4:38 pm, "seymour.shabow" <seymour.sha...@gmail.com> wrote:
> Gott Lieb? wrote:
> > How is 21 going to work, if you disable the credit button, as
> > mentioned previously?  What about adding center drains?  It should be
> > easy, just add an exception to the left and right drains.  I would be
> > curious how many balls go down the middle versus the outlanes.
>
> Well, I'd have to add a timer function to determine if the center drain
> was just a center drain or if it was a drain after the left and right
> drains..... the outhole switch trips in all drain cases ;)  I guess I
> can make it do the math, SDTM drains=all outhole drains - left drains -
> right drains.  One way needs math the timer way need finesse.
>
> I probably won't disable the credit button except for the tournament
> mode setting, which I haven't decided on 100% yet.

seymour-shabow

2/18/2011 12:08:00 PM

0

Gott Lieb? wrote:
> I just figured it would be something like:
>
> switch closure before outhole switch closure <> left drain OR right
> drain
>
> I'll stick to high level programming. :-)
>

That is high level programming.... that would probably work out easiest.

Did you draw a flow chart? ;)

-scott CARGPB#29

Gott Lieb?

2/18/2011 12:28:00 PM

0

NO, I don't do flow charts. :-| I code on the fly. It makes
debugging all the more fun! ;-)

Jim

On Feb 18, 7:07 am, "seymour.shabow" <seymour.sha...@gmail.com> wrote:

> That is high level programming.... that would probably work out easiest.
>
> Did you draw a flow chart? ;)
>
> -scott CARGPB#29