Making kdefx static

Andreas Pakulat apaku at
Fri Aug 3 22:04:10 BST 2007

On 03.08.07 16:48:13, Allen Winter wrote:
> I believe the earlier discussion on this issue, as shown below,
> is what we should do.  Note that you do not have an
> exemption to put in an entire new subsystem; rather
> an exemption to remove and cleanup in kdefx.
> IOW: trash kdefx in KDE 4.0.  Hopefully, we'll have either
> 1) Quasar in a future Qt 4.x release 2) parts of Quasar
> in a brand new kdefx in KDE 4.1+
> Yes, this might mean that some apps have to
> regress on some features.  I guess.  But, it is a .0.
> Or, those apps can temporarily copy over the kdefx
> code to their local source.

Hope you are aware that this is a quite huge undertaking and we're
talking about pretty core apps, like the background kcm, koffice parts,
the thumbnail slave, okular, kopete for just KImageEffect. No I have no
idea how hard it is to port away from that class, but there are 660
references, so unless this can be done with a script I doubt thats
doable in the current time frame for KDE 4.0. KPixmapEffect seems to be
used about the same amount.


You are a fluke of the universe; you have no right to be here.

More information about the kde-core-devel mailing list