[ANN] Go IMagick - ImageMagick cgo binding

[Herbert Fischer]

Greetings,

I'm happy to announce my ImageMagick bindings for Go. 

The entire MagickWand C API was mapped and probably is sufficient to do a lot. Some things are still missing or partially mapped, mostly things related to the MagickCore API.

I still consider it alpha work and I'm accepting contributions. 

Details about it may be found in the following link:

https://github.com/gographics/imagick

I hope you find it useful.

Herbert G. Fischer

[Job van der Zwan]

I ever am in a "I need ImageMagick for this"-situation (past experience indicates this WILL happen) I'll be very happy this exists. Thank you!

(Will you also take a stab at GraphicsMagick[1]?)

[1] http://www.graphicsmagick.org/wand/wand.html

[Herbert Fischer]

Why not? 

I only choose ImageMagick because some people advert it being more feature complete (has support to CMYKA) and also thread-safe [1], and since this was my first Go project using cgo, I could not tell if this is really important for Go (e.g. goroutines). Another thing I've found out is that GraphicsMagick is faster by default because it uses RAM as temporary space, and ImageMagick uses temporary files in disk and this can easily be changed [1]. Other argues that GM is faster because is a slimmed down version of IM [2]. It's also is really hard to choose but I kept IM because I really needed CMYKA support.

I would first try to make through some way to pre-select the prefered library in the same project, but I think this is not possible. I'm also looking for a solution of to make easier to use this binding with different versions of ImageMagick. Some people certainly will have some trouble building this binding in Ubuntu 12.10 (I had) since it's ImageMagick version is too old (6.7.7 against 6.8.5), misses some functions used in the binding and there is even some bug that someone swapped some API function names.

After writing this bindings In about 6 days, I'm considering porting IM or GM entirely to Go since it's relatively easy to port C to Go and we could easily benefit of Go's concurrency features and memory management.

[1] http://www.kitchensoap.com/2008/09/02/why-we-use-graphicsmagick/#comment-7344

[2] http://www.imagemagick.org/pipermail/magick-users/2011-April/023749.html

[Herbert Fischer]

I've just updated the Go Imagick with a go1 branch (the one "go get"able - for API stability) and lowered the minimum required ImageMagick version to 6.7.7 (the one present in Ubuntu 12.10 and Debian 7.0).

I've also updated and fixed some things in the README.

[anjan....@gmail.com]

"After writing this bindings In about 6 days, I'm considering porting IM or GM entirely to Go since it's relatively easy to port C to Go and we could easily benefit of Go's concurrency features and memory management."

+1

Did you make any progress on this ? Is it still in the plan ?

Thank you,

[Herbert Fischer]

Not alone. It's an herculean job.

I barely had time to use my own cgo bindings and any other project in Go recently.

I've heard that folks are using the binding, including the guy from goingo.net, so I think is doing well.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.