kwin/libkwineffects
Martin Gräßlin a348df0d34 Use properties in EffectWindow where possible instead of inheritance
If possible use the property to Toplevel or Client instead of the
pure virtual methods. This makes it easier to get a stable ABI.
Adding new methods to the class no longer requires to add a pure
virtual method.

From a performance point of view this change should not matter.
Most EffectWindow methods are not invoked during the repaint chain.
But only in response to an event like a window got added. There the
overhead does not really matter as well the previous implementation
made strong use of dynamic casts which are also not knwon for being
very fast.
2012-01-27 08:21:52 +01:00
..
anidata.cpp
anidata_p.h
CMakeLists.txt
kwinanimationeffect.cpp
kwinanimationeffect.h
kwinconfig.h.cmake
kwineffects.cpp Use properties in EffectWindow where possible instead of inheritance 2012-01-27 08:21:52 +01:00
kwineffects.h Use properties in EffectWindow where possible instead of inheritance 2012-01-27 08:21:52 +01:00
kwinglobals.cpp
kwinglobals.h
kwinglplatform.cpp
kwinglplatform.h
kwingltexture.cpp
kwingltexture.h
kwingltexture_p.h
kwinglutils.cpp
kwinglutils.h
kwinglutils_funcs.cpp
kwinglutils_funcs.h
kwinxrenderutils.cpp
kwinxrenderutils.h
Mainpage.dox
Messages.sh