Introducing image processors

[dicom]

Historically, ruby-dicom has had RMagick image methods integrated, for easy extraction and insertion of images from/to DICOM objects. However, not everyone is too happy with RMagick. It is resource intensive, it is not actively maintained any more, and it is a hassle to install on Windows.

Ideally, ruby-dicom should be able to utilize any image library for exporting/importing images. Therefore, I have started work to introduce the concept of image processors. After requiring ruby-dicom, the user may select which of the supported image libraries he wishes be used by the buildt in image methods. This has the advantage of making ruby-dicom even more modular and accessible, but another positive side effect is that I believe the image code will become cleaner.

As a starting point, RMagick and mini_magick will be the supported image processors.

[dicom]

The rewrite has definitely resulted in cleaner code, which Im quite happy about.

For those wishing to use :mini_magick instead of RMagick with ruby-dicom, version 3.2.1 (or higher) of the mini_magick gem is required.