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

[Martin T. Kutschker]

Michael Stucki wrote:
> 
> 
>>Sorry, but that's, *hmm* not quite in spirit of a general API.
>>
>>I guess I won't use Fireworks, but I'm really in favor of a solution
>>which allows one who wishes to do so, actually CAN write a
>>"Fireworks-plugin".
>>
>>All the talks now of switching to GD or GM only is IMHO a step in the
>>wrong direction.
> 
> It's not a step in the wrong direction! It is a much faster step than
> waiting for such a general API.
> 
> If GD + GM work fine (but only if this is the case, of course) then I see no
> reason for such an API anymore.
> 
> If you're not happy with this solution you can spend your time working on
> this, of course. But I won't.

Reverse situation for me. I'm not interested in a lock-down to just 
another lib. GIMP/Firework will probably offer the best results, but I 
expect them to be slow. GM is fine but is yet to be seen if there is 
widespread support fo it with ISPs.

I see no reason to rush things. I don't think that an API will dealy 
things indefintely if all willing parties work together. I estimate abou 
a month (calendar days, not work hours) overhead with all the 
discussion. Typo3 was stuck with GD/IM for a very long time. It can wait 
  a bit and 3.8 will not be ready for some time.

And certainly I'm not going to work on an API if there is no support by 
the community or other developers. If the common wisdom is that an API 
is an overkill or simply not worth any efforts, themn so be it.

Yep, I'm unhappy with GD/GM, but I can live with this disappointment.

Masi