kwin/effects/mousemark
Martin Gräßlin 76efe517a7 Turn built-in effects into a library kwin links against
As all effects have always been compiled into the same .so file it's
questionable whether resolving the effects through a library is useful
at all. By linking against the built-in effects we gain the following
advantages:
* don't have to load/unload the KLibrary
* don't have to resolve the create, supported and enabled functions
* no version check required
* no dependency resolving (effects don't use it)
* remove the KWIN_EFFECT macros from the effects

All the effects are now registered in an effects_builtins file which
maps the name to a factory method and supported or enabled by default
methods.

During loading the effects we first check whether there is a built-in
effect by the given name and make a shortcut to create it through that.
If that's not possible the normal plugin loading is used.

Completely unscientific testing [1] showed an improvement of almost 10
msec during loading all the effects I use.

[1] QElapsedTimer around the loading code, start kwin five times, take
average.

REVIEW: 115073
2014-01-24 14:13:59 +01:00
..
CMakeLists.txt CMake macros porting 2013-11-27 16:11:14 +01:00
mousemark.cpp Turn built-in effects into a library kwin links against 2014-01-24 14:13:59 +01:00
mousemark.desktop SVN_SILENT made messages (.desktop file) 2014-01-19 04:06:03 +00:00
mousemark.h MouseMark effect supports QPainter compositor 2014-01-09 13:29:40 +01:00
mousemark.kcfg Use KConfigXT in MouseMark Effect 2012-09-14 10:39:28 +02:00
mousemark_config.cpp KIntSpinBox -> QSpinBox in kwin/effects configs 2013-09-09 07:38:30 +02:00
mousemark_config.desktop SVN_SILENT made messages (.desktop file) 2014-01-19 04:06:03 +00:00
mousemark_config.h Use KConfigXT in MouseMark Effect 2012-09-14 10:39:28 +02:00
mousemark_config.ui KIntSpinBox -> QSpinBox in kwin/effects configs 2013-09-09 07:38:30 +02:00
mousemarkconfig.kcfgc Use KConfigXT in MouseMark Effect 2012-09-14 10:39:28 +02:00