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
zoom.cpp	Turn built-in effects into a library kwin links against	2014-01-24 14:13:59 +01:00
zoom.desktop	SVN_SILENT made messages (.desktop file)	2014-01-19 04:06:03 +00:00
zoom.h	Use Q_SLOTS and Q_SIGNALS instead of slots and signals	2013-07-24 09:46:54 +02:00
zoom.kcfg	Use KConfigXT in Zoom Effect	2012-09-14 10:39:28 +02:00
zoom_config.cpp	KIcon -> QIcon::fromTheme in kwin effects	2013-09-05 10:29:33 +02:00
zoom_config.desktop	SVN_SILENT made messages (.desktop file)	2014-01-19 04:06:03 +00:00
zoom_config.h	Use Q_SLOTS and Q_SIGNALS instead of slots and signals	2013-07-24 09:46:54 +02:00
zoom_config.ui	Use KShortcutsEditor directly instead of subclass	2013-09-09 06:57:06 +02:00
zoomconfig.kcfgc	Use KConfigXT in Zoom Effect	2012-09-14 10:39:28 +02:00