State of kdefx

Mosfet daniel.duley at verizon.net
Tue Jul 24 13:27:06 BST 2007


BTW: Remember I'm not on kde-core-devel so need to be CC'ed in order to see 
emails and reply properly. This is a reply to Zack's email which I read on 
the list archive ;-)

----

Hi Zack! That pretty much sounds like what we agreed on before, it's just the 
other developers weren't privy to our emails so were wondering what's up with 
KImageEffect ;-)

So to summarize for everyone else: I got a lot of fixes for KImageEffect if 
needed - most of the methods have been rewritten *years ago* compared to what 
is in SVN and is chock full of neat stuff (TM).

But Zack, (as well as several other developers), don't seem to like the API 
and have a lot of good new ideas. So the plan was to use Zack's new library 
and I'd port the things that are still relevant to it. It appears this won't 
be ready until KDE4.1, tho.

That leaves the question about what to do about KDE4.0. Zack as well as 
everyone else seems to feel an effect library won't be needed but I am not 
sure about this. I don't know where the meme started that KImageEffect is 
only used by widget styles but that is not true. It's used by several 
applications both in and out of KDE SVN. Everyone here who is stating 99% of 
the library is not used by anything or only used by widget styles is wrong :P

Anyways, I still think it should be removed from kdelibs if it is going to be 
replaced by Zack's library. In the meantime I can make an interm library with 
an API similiar to KImageEffect that people can use until KDE4.1. I already 
have this for my own projects - it's called "Blitz". When it's ready I can 
stick it on kde ftp or something. In the porting docs people can be directed 
to use that until KDE4.1 is released, then use the new library.

Anyways, that's my 2cents.




More information about the kde-core-devel mailing list