[Typo3-dev] Image Processing API - getting rid of IM

[Daniel Brün]

Hi Masi!

> Please note that the in-memory formats are incompatible. A GD "object" 
> cannot be processed by PHP-ImageMagick or any other PHP extension.
> 
> I am talking about chaining commands that involves multiple sub-APIs. In 
> ths scenario different implementations may be invoked (GD, ImageMagick, 
> GIMP, ...).

Nonono. You can implement the API with a class that you may call 
"performance Image Processing" that makes use of GD, IM and GD at the 
same time. Of course every single Image-Processing-class has to deal 
with the different formats it uses inside itself.

> I am thinking about an algorithm that chooses the best path for you. 
> Either try to keep as much as possible im memory or choose always the 
> besst tool.

How should an algorithm be able to make that choice? I think the 
developer makes the choice when developing the class.

> If GD2 did all the stuff, we wouldn't need this API.

Exactly. Even though having a class that fulfills the 
Image-Processing-API and only uses GD would still be cleaner than 
hardcoding GD into the system. But anyways, if GD had all the features 
we need, integrating this into T3 would be at least a huge step into the 
right direction.

> BTW, I'd choose the Typ3 service mechanism as a basis for the API.

Yes, maybe.

Cheers,

Dan.