yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/effects/CMakeLists.txt

196 lines
5.6 KiB
Text
Raw Normal View History

Adjust effects_builtins for new ki18n * Use ki18n_wrap_ui for ui files * define TRANSLATION_DOMAIN in CMakeLists.txt
2014-04-29 06:25:19 +00:00
# KI18N Translation Domain for this library
[effects] Support building the effect_builtins without need to link the lib This change allows to include the effect_builtins.cpp into the build of e.g. a kcm without having to link against all effects. The use case for this is when one needs to resolve just the name of an effect without wanting to hard code the name.
2015-01-28 08:46:31 +00:00
add_definitions(-DTRANSLATION_DOMAIN=\"kwin_effects\" -DEFFECT_BUILTINS)
Adjust effects_builtins for new ki18n * Use ki18n_wrap_ui for ui files * define TRANSLATION_DOMAIN in CMakeLists.txt
2014-04-29 06:25:19 +00:00
[effects] Allow Built-In Effects using xcbutils.h xcbutils.h has quite a few inline only implementations such as Xcb::Atom, the Wrappers, Xcb::Window and the convenient methods. Thus there is nothing wrong with using it from the built-in Effects. Xcb::Atom is used in Glide and Logout Effect to get the atom. To keep the logic of the existing code it got extended by a bool isValid() which gets the reply and returns true if the atom is set. REVIEW: 117587
2014-04-16 12:27:48 +00:00
include_directories(${KWIN_SOURCE_DIR}) # for xcbutils.h
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
set(kwin_effect_OWN_LIBS
kwineffects
)
[kwin] Create an own library for kwinxrenderutils XRenderUtils are split out of kwineffects and are an own library just like kwinglutils is an own library. The library gets always build and is linked in KWin core unconditionally (as it's used in outline) and conditionally in kwineffects (PaintClipper) and the built in effects depending on XRender build option.
2014-03-16 14:31:23 +00:00
if( KWIN_HAVE_XRENDER_COMPOSITING )
set(kwin_effect_OWN_LIBS ${kwin_effect_OWN_LIBS} kwinxrenderutils)
endif()
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
set(kwin_effect_KDE_LIBS
Depend on ConfigGui through KConfigSkeleton
2014-03-24 12:02:48 +00:00
KF5::ConfigGui
Port to KF5 renaming changes
2013-12-11 20:41:47 +00:00
KF5::ConfigWidgets
Adjust to new KGlobalAccel framework
2013-12-09 08:33:58 +00:00
KF5::GlobalAccel
Port to KF5 renaming changes
2013-12-11 20:41:47 +00:00
KF5::I18n
KF5::WindowSystem
Change KF5::plasma to KF5::Plasma Library name has changed in plasma-framework to bring it in line with KF5:CamelCasing naming.
2013-10-15 23:36:24 +00:00
KF5::Plasma # screenedge effect
Port to KF5 renaming changes
2013-12-11 20:41:47 +00:00
KF5::IconThemes
KF5::Service
[effects] Show a notification when a screenshot got saved to file Summary: Inform the user about the path to where a screenshot got saved through a notification. This is helpful on the one hand that the user sees that the screenshot got saved and from a security perspective that the user is informed when a screenshot is taken through the dbus interface. It doesn't prevent non-authorized screenshot taking, but at least the user is informed about it. Reviewers: #kwin, #plasma, #vdg Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D3376
2016-11-16 08:50:18 +00:00
KF5::Notifications # screenshot effect
Use a QDeclarativeView for button views in Present Windows and Desktop Grid Declarative UI++ REVIEW: 109409
2013-03-11 08:33:38 +00:00
)
set(kwin_effect_QT_LIBS
Fix linking and includes Seems like there were some changes, we need more explicit linking.
2013-10-02 13:23:56 +00:00
Qt5::Concurrent
Use Qt5:: in target link libraries in KWin
2013-08-20 07:10:18 +00:00
Qt5::DBus
Qt5::Quick
Qt5::X11Extras
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
)
set(kwin_effect_XLIB_LIBS
More fine grained linking than X11_LIBRARIES Use X11_X11_LIB and actually needed additional libs instead of everything coming with X11_LIBRARIES. REVIEW: 109141
2013-03-04 07:50:23 +00:00
${X11_X11_LIB}
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
)
set(kwin_effect_XCB_LIBS
[kwin] Use imported targets for all XCB libs Requires 04f78489265b6e52cabd2980dfc417abeee3a695 from ECM
2014-02-25 14:48:39 +00:00
XCB::XCB
XCB::IMAGE
XCB::XFIXES
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
)
if( KWIN_HAVE_XRENDER_COMPOSITING )
[kwin] Use imported targets for all XCB libs Requires 04f78489265b6e52cabd2980dfc417abeee3a695 from ECM
2014-02-25 14:48:39 +00:00
set(kwin_effect_XCB_LIBS ${kwin_effect_XCB_LIBS} XCB::RENDER)
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
endif()
Remove build checks for gles or gl Also removes the building of the kwinglesutils, there's only kwinglutils now. REVIEW: 125865
2015-10-30 12:47:37 +00:00
set(kwin_effect_OWN_LIBS ${kwin_effect_OWN_LIBS} kwinglutils)
Split the libs we link to into multiple variables Using a lib variable for: * own libs * qt libs * kde libs * xlib libs * xcb libs and link those groups together in target_link_libraries. This should make the code easier to read and easier to support in future for some time both Qt4 and Qt5.
2013-02-25 11:05:36 +00:00
Build effects twice - once with GL, once with GLES
2011-07-17 15:27:14 +00:00
macro( KWIN4_ADD_EFFECT_BACKEND name )
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-17 12:46:04 +00:00
add_library( ${name} SHARED ${ARGN} )
[kwin] Make built in effects link all libraries privately REVIEW: 116838
2014-03-16 14:49:44 +00:00
target_link_libraries( ${name} PRIVATE ${kwin_effect_OWN_LIBS} ${kwin_effect_KDE_LIBS} ${kwin_effect_QT_LIBS} ${kwin_effect_XLIB_LIBS} ${kwin_effect_XCB_LIBS})
Cmake cleanup: empty endfoo()
2013-02-25 10:44:26 +00:00
endmacro()
Move testing/demo effects (those not meant for end users) to test/ subdir and don't build them by default. svn path=/trunk/KDE/kdebase/workspace/; revision=732055
2007-11-02 17:28:21 +00:00
branches/work/kwin_composite becomes new trunk kwin. svn path=/trunk/KDE/kdebase/workspace/; revision=659202
2007-04-29 17:35:43 +00:00
# Adds effect plugin with given name. Sources are given after the name
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
macro( KWIN4_ADD_EFFECT name )
Improve CMake usage It's basically a run of the port-cmake.sh script in here, mostly the changes are the following: - Using KF5::* targets - Using the proper macros, following recent developments in frameworks
2013-11-15 12:37:47 +00:00
kwin4_add_effect_backend(kwin4_effect_${name} ${ARGN})
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-17 12:46:04 +00:00
set_target_properties(kwin4_effect_${name} PROPERTIES VERSION 1.0.0 SOVERSION 1 )
[kwin] Follow Qt's OpenGL choice for KWin As KWin indirectly uses Qt's OpenGL through QtQuick we need to ensure to not mix OpenGL and OpenGLES. So we have to built KWin only against OpenGL if Qt is built against OpenGL and we have to built KWin only against GLESv2 if Qt is built against GLESv2. This means the kwin_gles binary is no more. There is only kwin which either links GL or GLESv2.
2013-10-14 07:04:03 +00:00
set_target_properties(kwin4_effect_${name} PROPERTIES OUTPUT_NAME ${KWIN_NAME}4_effect_${name})
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-17 12:46:04 +00:00
install(TARGETS kwin4_effect_${name} ${INSTALL_TARGETS_DEFAULT_ARGS} )
Build effects twice - once with GL, once with GLES
2011-07-17 15:27:14 +00:00
Cmake cleanup: empty endfoo()
2013-02-25 10:44:26 +00:00
endmacro()
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
# Install the KWin/Effect service type
install( FILES kwineffect.desktop DESTINATION ${SERVICETYPES_INSTALL_DIR} )
* Rearrange CMakeLists.txt to be (IMHO) a bit more logical. * Move drunken, shakymove and wavywindows from builtins to tests. Probably they should also be prefixed with test or demo, but I'm not bothered enough to do it myself yet. svn path=/trunk/KDE/kdebase/workspace/; revision=667378
2007-05-22 16:58:10 +00:00
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
# Create initial variables
set( kwin4_effect_include_directories )
branches/work/kwin_composite becomes new trunk kwin. svn path=/trunk/KDE/kdebase/workspace/; revision=659202
2007-04-29 17:35:43 +00:00
[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-17 13:56:11 +00:00
set( kwin4_effect_builtins_sources
logging.cpp
effect_builtins.cpp
blur/blur.cpp
blur/blurshader.cpp
[effects] Add a colorpicker effect Summary: The effect exports itself to DBus as object "/ColorPicker" and provides an own interface "org.kde.kwin.ColorPicker". It has one exported method to DBus "pick" which returns a QColor. When invoked an interactive position picking selection is started. If it ends the effect reads the color value at the picked position from the OpenGL color buffer. This implements T4568. Reviewers: #kwin, #plasma_on_wayland, broulik Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D3480
2016-11-24 07:07:51 +00:00
colorpicker/colorpicker.cpp
[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-17 13:56:11 +00:00
cube/cube.cpp
cube/cube_proxy.cpp
[effects] Move the Desktop Cube Animation effect to its own directory Summary: Just little tidying. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15725
2018-09-24 06:36:11 +00:00
cubeslide/cubeslide.cpp
[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-17 13:56:11 +00:00
coverswitch/coverswitch.cpp
desktopgrid/desktopgrid.cpp
diminactive/diminactive.cpp
flipswitch/flipswitch.cpp
glide/glide.cpp
invert/invert.cpp
lookingglass/lookingglass.cpp
magiclamp/magiclamp.cpp
magnifier/magnifier.cpp
mouseclick/mouseclick.cpp
mousemark/mousemark.cpp
presentwindows/presentwindows.cpp
presentwindows/presentwindows_proxy.cpp
resize/resize.cpp
showfps/showfps.cpp
[effects/showpaint] Use a shortcut to toggle the effect Summary: The Show Paint effect is useful when debugging repaint regions issued by effects. The only headache with it is necessity to enable/disable it. Consider the following workflow: * Do some change to an effect; * Compile KWin (or the effect); * Go to System Settings and enable the Show Paint effect; * Test effect, check repaint regions, etc; * Disable the Show Paint effect; * Go to the step 1. This workflow is really exhausting. Also, when testing repaints in a nested compositor, things become quite messy. Because purpose of this effect is to debug repaints (and because this effect is not meant for daily usage), I think that's fine to change how it's activated. This patch improves the workflow by changing the way how this effect gets activated. Instead of enabling/disabling it, one can just use a shortcut to activate or deactivate the effect. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: broulik, davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15703
2018-09-23 07:49:17 +00:00
showpaint/showpaint.cpp
[effects/slide] Add 'Duration' option Summary: At the moment, there is no way to tweak duration of the slide animation. This change adds a configuration module so it is possible to change the duration. Test Plan: * enable virtual desktops * go to `System Settings > Desktop Behaviour > Desktop Effects` and select Slide effect under "Virtual Desktop Switching Animation" * click settings/options button and change duration Reviewers: #kwin, #plasma, graesslin Reviewed By: #kwin, #plasma, graesslin Subscribers: graesslin, plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D9382
2017-12-30 17:17:13 +00:00
slide/slide.cpp
[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-17 13:56:11 +00:00
thumbnailaside/thumbnailaside.cpp
[effects] Add new effect for touch point visualization Summary: The new effect is based on the mouse click effect and uses the same rendering code (this could be improved by merging them better). Unlike mouse click there is no keyboard shortcut needed to activate: as soon as the effect is loaded all touch points are visualized. The visualization creates an animated circle for each touch down position, motion and up position. The ids are tracked and each touch id gets the same color. The first ten different touch ids get a different color. As touch ids are stable the first finger will always have the same color. Reviewers: #kwin, #plasma_on_wayland, bshah Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2464
2016-08-16 18:16:41 +00:00
touchpoints/touchpoints.cpp
[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-17 13:56:11 +00:00
trackmouse/trackmouse.cpp
windowgeometry/windowgeometry.cpp
wobblywindows/wobblywindows.cpp
zoom/zoom.cpp
)
[effects] Combine all shaders in resources One resource is used for shader version 1.10 and one for version 1.40. The ideas behind this change is to remove the locating of the shader sources and also to fix that user provided shaders could be loaded instead of the original ones (possible attack vector on Wayland). To simplify the ShaderManager provides a new method call to load the shader from the resource. This means the effects don't need to duplicate the check for the shader version any more and also don't need to duplicate the file reading functionality. REVIEW: 126905
2016-01-26 14:38:42 +00:00
qt5_add_resources( kwin4_effect_builtins_sources shaders.qrc )
[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-17 13:56:11 +00:00
kconfig_add_kcfg_files(kwin4_effect_builtins_sources
blur/blurconfig.kcfgc
cube/cubeconfig.kcfgc
[effects] Move the Desktop Cube Animation effect to its own directory Summary: Just little tidying. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15725
2018-09-24 06:36:11 +00:00
cubeslide/cubeslideconfig.kcfgc
[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-17 13:56:11 +00:00
coverswitch/coverswitchconfig.kcfgc
desktopgrid/desktopgridconfig.kcfgc
diminactive/diminactiveconfig.kcfgc
[effects] Introduce kcfg for FallApart effect Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D3374
2016-11-16 07:13:38 +00:00
fallapart/fallapartconfig.kcfgc
[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-17 13:56:11 +00:00
flipswitch/flipswitchconfig.kcfgc
glide/glideconfig.kcfgc
lookingglass/lookingglassconfig.kcfgc
magiclamp/magiclampconfig.kcfgc
magnifier/magnifierconfig.kcfgc
mouseclick/mouseclickconfig.kcfgc
mousemark/mousemarkconfig.kcfgc
presentwindows/presentwindowsconfig.kcfgc
resize/resizeconfig.kcfgc
showfps/showfpsconfig.kcfgc
[effects/slide] Add 'Duration' option Summary: At the moment, there is no way to tweak duration of the slide animation. This change adds a configuration module so it is possible to change the duration. Test Plan: * enable virtual desktops * go to `System Settings > Desktop Behaviour > Desktop Effects` and select Slide effect under "Virtual Desktop Switching Animation" * click settings/options button and change duration Reviewers: #kwin, #plasma, graesslin Reviewed By: #kwin, #plasma, graesslin Subscribers: graesslin, plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D9382
2017-12-30 17:17:13 +00:00
slide/slideconfig.kcfgc
[effects] Introduce kcfg for SlidingPopups Summary: Uses the normal animationTime kcfg settings. Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D3375
2016-11-16 08:02:44 +00:00
slidingpopups/slidingpopupsconfig.kcfgc
[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-17 13:56:11 +00:00
thumbnailaside/thumbnailasideconfig.kcfgc
trackmouse/trackmouseconfig.kcfgc
windowgeometry/windowgeometryconfig.kcfgc
wobblywindows/wobblywindowsconfig.kcfgc
zoom/zoomconfig.kcfgc
)
Fade effect goes JavaScript Our first effect written in JavaScript to replace an existing C++ effect. Fade effect has been chosen as it has shown to be problematic in the past and would have needed a migration to AnimationEffect anyway.
2012-02-02 13:39:39 +00:00
# scripted effects
Rewrite of dialog parent effect in JavaScript REVIEW: 110802
2013-06-03 13:05:22 +00:00
add_subdirectory( dialogparent )
[effects/dimscreen] Port to JavaScript Summary: The ported effect looks quite similar to the C++ version except one thing: it works correctly when user activates/deactivates a full screen effect, for example the Desktop Cube effect. Other than that, there are no behavioral or visual differences. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16452
2018-10-25 13:48:47 +00:00
add_subdirectory( dimscreen )
add eye On Screen effect for showing desktop resembles the homescreen effect on "eye" OS REVIEW: 122679
2015-03-30 09:38:54 +00:00
add_subdirectory( eyeonscreen )
Fade effect goes JavaScript Our first effect written in JavaScript to replace an existing C++ effect. Fade effect has been chosen as it has shown to be problematic in the past and would have needed a migration to AnimationEffect anyway.
2012-02-02 13:39:39 +00:00
add_subdirectory( fade )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
add_subdirectory( fadedesktop )
[effects] Split the Fade effect Summary: Currently, we have three effects that can be used to animate the appearing of toplevel windows(fade, glide, scale) and one can enable all three of them, which seems to be wrong. It doesn't make sense to have glide and scale effect enabled, for example. We couldn't put all three effects into an exclusive group before because the fade effect animates not only toplevel windows but also popups. So, if all three effects are in an exclusive group and you enable glide effect, for example, then tooltips and other popups won't be faded in/out. This patch splits the fade effect into two: the first effect (called Fade) animates toplevel windows and the other one (called Fading Popups) animates popup windows. Test Plan: Have been using the Fading Popups effect in combination with the Scale effect for a couple of days. Haven't noticed any significant differences between the new combination (Fading Popups + Scale) and the old combination (Fade + Scale). Reviewers: #kwin, #plasma, #vdg, graesslin Reviewed By: #kwin, #plasma, graesslin Subscribers: graesslin, abetts, ngraham, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16836
2018-11-03 15:42:31 +00:00
add_subdirectory( fadingpopups )
Desaturate non-responsive windows When an application is not responding, its window is desaturated to communicate this. Also "(Not Responding)" is added to the title bar. Differential Revision: https://phabricator.kde.org/D5245
2017-04-05 09:16:23 +00:00
add_subdirectory( frozenapp )
Rewrite of Login effect to JavaScript Main motivation for this rewrite is the fact that the login effect had been designed under the assumption that there is only one login splash window. This assumption does no longer hold with the QML based splash, which creates a window per screen. By using a JavaScript based effect, the animation effect is implicityly used which supports animating multiple windows at the same time in a better and safer way. BUG: 313061 FIXED-IN: 4.11 REVIEW: 108403
2013-01-14 07:38:18 +00:00
add_subdirectory( login )
new logout effect Summary: new logout effect: it's just a slow fade in of the logout greeter (window is usable immediately tough Test Plan: logout greeter now fades in without setting the window opacity manually Reviewers: graesslin, #plasma Reviewed By: graesslin, #plasma Subscribers: broulik, plasma-devel, kwin, #kwin Tags: #plasma Differential Revision: https://phabricator.kde.org/D5045
2017-03-15 16:47:13 +00:00
add_subdirectory( logout )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
add_subdirectory( maximize )
Morphingpopups effect, to animate tooltips this effect, derived from the Maximize one, will take the place of the manual window position animation that Plasma tooltip are using. this should cause less problems as animationg positions on X is very error prone, plus it's less jarring when the tooltip sizes changes too, since that gets animated as well (behavior similar to Windows7 taskbar tooltips) REVIEW:126968
2016-02-16 15:44:41 +00:00
add_subdirectory( morphingpopups )
[effects/scale] Port to JavaScript Summary: Now, when the scripting effects API has all required ingredients to port the Scale effect to JavaScript we finally can do it. The main rationale for porting this effect to JavaScript is that scripted effects API lets us focus more on what we want instead of "how". Visually, the ported version doesn't deviate from the C++ version. Test Plan: * Enable the Scale effect; * Open/close a window. Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16478
2018-10-27 21:27:25 +00:00
add_subdirectory( scale )
[effects] Re-implement the Minimize Animation effect in JavaScript Summary: There were several reasons to rewrite the Minimize Animation effect in JavaScript: to simplify code and to get rid of full repaints. One could say that nothing prevents us from calculating the dirty region in postPaintScreen or postPaintWindow and it is correct, but with the scripting effects API the dirty region will be calculated for us, so we can focus more on "what we want" instead of "how". Visually, the "old" effect and the rewritten one look quite the same. Except one tiny bit: if a window doesn't have an icon in the task manager, it won't be animated. The reason for that is the purpose of this effect is to show where the window will be after it's minimized, if the window doesn't have icon in the task manager, one can't click at the center of the screen to unminimize the window. There is one significant change, the name of the effect was changed to "Squash". If we put this effect and the Magic lamp effect under "Window Minimize Animation" category (or if we add some "heading" label), then the old name and the name of the category would "conflict". The new name was suggested by Nate Graham and it very closely describes what the effect does. "Scale" doesn't fit this effect because while a window is being animated, its aspect ratio is not preserved. Reviewers: #kwin, #plasma, davidedmundson Reviewed By: #kwin, #plasma, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16372
2018-09-23 17:07:48 +00:00
add_subdirectory( squash )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
add_subdirectory( translucency )
Add Window Aperture effect for showing the desktop It moves windows to nearest corners
2015-03-28 23:15:57 +00:00
add_subdirectory( windowaperture )
FadeDesktop effect ported to JavaScript
2012-02-02 16:58:31 +00:00
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
###############################################################################
# Built-in effects go here
# Common effects
[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-17 13:56:11 +00:00
add_subdirectory( desktopgrid )
add_subdirectory( diminactive )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
include( fallapart/CMakeLists.txt )
include( highlightwindow/CMakeLists.txt )
Helper effect for KScreen integration This effect is controlled by KScreen. It fades out all windows when KScreen requests this and gives feedback to KScreen once all windows are faded out. This allows KScreen to adjust the screens in a flicker free way. REVIEW: 110661 BUG: 319994 FIXED-IN: 4.11
2013-05-27 08:45:22 +00:00
include( kscreen/CMakeLists.txt )
[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-17 13:56:11 +00:00
add_subdirectory( magiclamp )
add_subdirectory( presentwindows )
add_subdirectory( resize )
New Glow on approaching Screen Edge Effect Feature stolen from hidden Plasma Panel now available for all edges on approach by mouse.
2013-01-31 12:31:49 +00:00
include( screenedge/CMakeLists.txt )
[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-17 13:56:11 +00:00
add_subdirectory( showfps )
[effects/showpaint] Use a shortcut to toggle the effect Summary: The Show Paint effect is useful when debugging repaint regions issued by effects. The only headache with it is necessity to enable/disable it. Consider the following workflow: * Do some change to an effect; * Compile KWin (or the effect); * Go to System Settings and enable the Show Paint effect; * Test effect, check repaint regions, etc; * Disable the Show Paint effect; * Go to the step 1. This workflow is really exhausting. Also, when testing repaints in a nested compositor, things become quite messy. Because purpose of this effect is to debug repaints (and because this effect is not meant for daily usage), I think that's fine to change how it's activated. This patch improves the workflow by changing the way how this effect gets activated. Instead of enabling/disabling it, one can just use a shortcut to activate or deactivate the effect. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: broulik, davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15703
2018-09-23 07:49:17 +00:00
add_subdirectory( showpaint )
[effects/slide] Add 'Duration' option Summary: At the moment, there is no way to tweak duration of the slide animation. This change adds a configuration module so it is possible to change the duration. Test Plan: * enable virtual desktops * go to `System Settings > Desktop Behaviour > Desktop Effects` and select Slide effect under "Virtual Desktop Switching Animation" * click settings/options button and change duration Reviewers: #kwin, #plasma, graesslin Reviewed By: #kwin, #plasma, graesslin Subscribers: graesslin, plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D9382
2017-12-30 17:17:13 +00:00
add_subdirectory( slide )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
include( slideback/CMakeLists.txt )
a new effect: windows with the atom _KDE_SLIDE set on them (composed by a number identifying north/south/west/east and a screen coord) will appear with a slide animation. used for popups that come out of panels svn path=/trunk/KDE/kdebase/workspace/; revision=1001604
2009-07-23 19:06:50 +00:00
include( slidingpopups/CMakeLists.txt )
[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-17 13:56:11 +00:00
add_subdirectory( thumbnailaside )
add_subdirectory( windowgeometry )
add_subdirectory( zoom )
Effects' config modules don't depend on opengl svn path=/trunk/KDE/kdebase/workspace/; revision=727695
2007-10-21 13:44:40 +00:00
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
# OpenGL-specific effects
[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-17 13:56:11 +00:00
add_subdirectory( blur )
stub for the background contrast effect * a copy of the blur shader to become a copy of the background contrast effect * contrastshader actually doing the light modification * don't expand/shrink the area
2013-12-01 19:28:57 +00:00
include( backgroundcontrast/CMakeLists.txt )
[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-17 13:56:11 +00:00
add_subdirectory( coverswitch )
add_subdirectory( cube )
[effects] Move the Desktop Cube Animation effect to its own directory Summary: Just little tidying. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15725
2018-09-24 06:36:11 +00:00
add_subdirectory( cubeslide )
[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-17 13:56:11 +00:00
add_subdirectory( flipswitch )
add_subdirectory( glide )
add_subdirectory( invert )
add_subdirectory( lookingglass )
add_subdirectory( magnifier )
add_subdirectory( mouseclick )
add_subdirectory( mousemark )
Remove define KWIN_HAVE_OPENGL_COMPOSITING Due to changes in build system we have always either OpenGL or OpenGL ES. This allows to remove the KWIN_HAVE_OPENGL_COMPOSITING define. In the effects the define is kept as KWIN_HAVE_OPENGL which can be used in future to build also an XRender only effect system.
2011-08-13 13:21:51 +00:00
include( screenshot/CMakeLists.txt )
[kwin] Drop the KWIN_MOBILE_EFFECTS build option It's no longer needed as there won't be a KWin version specific to Plasma Active. We want to have runtime adjustments of all parts in the next version of Plasma. REVIEW: 116563
2014-03-03 10:20:03 +00:00
include( sheet/CMakeLists.txt )
include( snaphelper/CMakeLists.txt )
include( startupfeedback/CMakeLists.txt )
[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-17 13:56:11 +00:00
add_subdirectory( trackmouse )
add_subdirectory( wobblywindows )
branches/work/kwin_composite becomes new trunk kwin. svn path=/trunk/KDE/kdebase/workspace/; revision=659202
2007-04-29 17:35:43 +00:00
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
###############################################################################
branches/work/kwin_composite becomes new trunk kwin. svn path=/trunk/KDE/kdebase/workspace/; revision=659202
2007-04-29 17:35:43 +00:00
Cleaned up the effects/ directory by moving each individual effect into its own directory, cleaned up the effect config macros and renamed "MakeTransparent" to "Translucency" so that it matches its visible name. svn path=/trunk/KDE/kdebase/workspace/; revision=921749
2009-02-05 15:35:38 +00:00
# Add the builtins plugin
Improve CMake usage It's basically a run of the port-cmake.sh script in here, mostly the changes are the following: - Using KF5::* targets - Using the proper macros, following recent developments in frameworks
2013-11-15 12:37:47 +00:00
kwin4_add_effect( builtins ${kwin4_effect_builtins_sources} )
Reference in a new issue Copy permalink