[Typo3-dev] Image Processing API - getting rid of IM
Martin T. Kutschker
Martin.no5pam.Kutschker at blackbox.n0spam.net
Tue Sep 21 11:08:28 CEST 2004
Daniel Brün wrote:
> Hi Masi!
>
> Martin T. Kutschker wrote:
>
>> 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.
>
> That's right, design-wise. And this is what Michael Stucki and me
> thought of first, too (see first post in this thread).
> BUT, defining a general image processing API is not as simple as it
> might seem and some major changes would have to be applied to the core.
I don't think it's easy, but I hope it's actually not hard.
> My first guess would be to develop some kind of base-interface-class
> that has to be implemented by a class using whatever image-processing
> library. In order to do so, a set of useful image-processing-operations
> should be investigated, first.
Sounds reasonable.
If more are willing we could do some discussion here or get us a new
group created. I'm willing to devote time on the API (design and
implementation of the service).
I'm not investigating Fireworks or GIMP. I ask everybody interested in
these options to do research and contribute to the API talks.
> In the end this will take some time before it is going to work properly.
> Because of that, I would not mind to make a "quick" fix, so GM is
> supported, first (remember: there is NO perfectly working solution for
> windows out there right now).
For GM I guess it'd be the best to hack the code into
t3lib_stdGraphpc.php. I'd make it just another GFX option, so IM and GM
can live in the same come.
Masi
More information about the TYPO3-dev
mailing list