You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
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
11 years ago
..
autotests
CMakeLists.txt
Mainpage.dox
Messages.sh
anidata.cpp
anidata_p.h
kwinanimationeffect.cpp
kwinanimationeffect.h
kwinconfig.h.cmake
kwineffects.cpp
kwineffects.h [kwin] Create one plugin per effect configuration 11 years ago
kwinglcolorcorrection.cpp
kwinglcolorcorrection.h
kwinglcolorcorrection_p.h
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