[Typo3-dev] Image Processing API - getting rid of IM
Christian Jul Jensen
christian at jul.net
Tue Sep 21 15:15:12 CEST 2004
Daniel Brün <dbruen at saltation.de> writes:
> 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. The only point against such an API is development time, which I
> do not have to offer right now.
I'm not sure if it's actually the case , you'll probably end up
spending lot's of time making sure it works everywhere anyhow. But
admitted I haven't looked closely at what changes are actually needed.
> If someone has the time to define a fresh API based on design
> patterns... go ahead!
> 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.
>
> 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).
I'm absolutely in favor of an API, I'm sure it's worth it on long
terms. And I would love being part of doing it, and might even get
some time to during this fall. (That's not a promise :) )
--
Julle
More information about the TYPO3-dev
mailing list