Martin Gräßlin f9e0a8b597 [kwin] Create one plugin per effect configuration ... There are no advantages for the effects KCM to have all the effect config modules in one plugin. By having a plugin per effect we can use the KPluginTrader to easily find the configuration plugin for a given effect and load it. To make this possible the following changes are done: * config_builtins.cpp is deleted * add_subdirectory is used for all effects which have a config module * toplevel CMakeLists.txt contains the sources again for the effects which have a config module, but effects which don't have a config module are still included and thus the macro is still used * plugin created for the config module, name pattern is: kwin_effectname_config * plugin installed to ${PLUGIN_INSTALL_DIR}/kwin/effects/configs * desktop file adjusted to new plugin name and keyword removed * desktop file converted to json as meta data and no longer installed * Uses K_PLUGIN_FACTORY_WITH_JSON * Macros for config are dropped from kwineffects.h REVIEW: 116854		2014-03-25 15:37:35 +01:00
..
CMakeLists.txt	[kwin] Create one plugin per effect configuration	2014-03-25 15:37:35 +01:00
magiclamp.cpp	Turn built-in effects into a library kwin links against	2014-01-24 14:13:59 +01:00
magiclamp.desktop	[kwin/effects] Put all minimize effects into an exclusive category	2014-03-12 16:32:42 +01:00
magiclamp.h	Use mgraesslin@kde.org for my mail address in Copyright and AboutData	2013-03-12 13:17:53 +01:00
magiclamp.kcfg	Use KConfigXT in MagicLamp effect	2012-09-19 09:29:27 +02:00
magiclamp_config.cpp	[kwin] Create one plugin per effect configuration	2014-03-25 15:37:35 +01:00
magiclamp_config.desktop	[kwin] Create one plugin per effect configuration	2014-03-25 15:37:35 +01:00
magiclamp_config.h	Use Q_SLOTS and Q_SIGNALS instead of slots and signals	2013-07-24 09:46:54 +02:00
magiclamp_config.ui	Use KConfigXT in MagicLamp effect	2012-09-19 09:29:27 +02:00
magiclampconfig.kcfgc	Use KConfigXT in MagicLamp effect	2012-09-19 09:29:27 +02:00