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

[Daniel Brün]

Hi Masi!

> Typo3 uses currently a mixture of ImageMagick and GD/GD2.
No Problem! The php-class that fulfills the Image-Processing-API can 
make use of whatever libraries it wants to... IM, GM, GD8, PhotoShop ;-)

> 
> Typo3 performs varios classes of actions with images
> 
> * format conversion (eg PNG->JPEG)
> * resizing/resampling
> * effect processing (gray scaling, composition, etc)
> * text processing (ie apllying of text onto an image)
> 
> AFAIK, there will arise the problem that not all "image libraries" will 
> support all of the described functions.

That's right, but it's not necessary, either, see above.

> One approach could be to define sub-APIs for the image-API, so eg I 
> could do format conversions with GD, but text processing with 
> ImageMagick, etc

Yes, that's the way we thought it should be!

> The above solution has the disadvantage that chaining of operations 
> becomes complicated. Possibly a high number of temporary files will be 
> created.

The Image-Processing-class keeps an image in memory for multiple 
operations on it. This can not work with IM though, because IM only 
operates on files.

> AFAIK this is already the case but I thought it might be interesting to 
> use PHP extensions and in-memory image-processing (eg with GD or the PHP 
> version of ImageMagick).

It would be perfect if GD2 could do all the stuff, so that no IM is 
needed anymore. My only problem with the iMagick-extension of PHP is its 
alpha-status.

> Anyway I'm all for it. But please let's do stuff right. IMHO there is no 
> point in being 100% (TS) backwards compatible as the current API is 
> highly ImageMagick orientated. Better create a new API and make stdimg 
> (trlib) a wrapper for the new stuff.

Well, I don't need backwards compatibility, but Kasper and most other 
folks on the list will scream if the new solution is not...



Cheers,

Dan.