State of kdefx

[Allen Winter]

On Tuesday 24 July 2007 7:17:06 am Zack Rusin wrote:
> On Friday 20 July 2007 06:22:33 am Mosfet wrote:
> > Hey, I see you all are finally noticing kdefx is broken again ;-)

> So personally I just feel it makes way more sense to do it properly for 4.1 
> rather than just put something in for 4.0. It's just not a showstopper for 
> 4.0 and applications/libraries that require some image effect as part of some 
> core functionality can just copy and paste the given effect in. 
> These applications will likely require something very special and instead of 
> trying to frantically get a whole image manipulation framework ready and 
> optimized for 4.0 (at, in my experience, great expense to its API) we can 
> simply give ourselves a little bit of extra time and do it properly for 4.1.
> 

Yes, we are in API freeze mode now.  So the decision is already made for 4.0.
I believe the plan is to remove most, if not all, of the current kdefx for 4.0.
 
Matthew Woehlke has an exemption to kill what needs to be killed in kdefx.

-Allen