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

65 lines
1.6 KiB
Text
Raw Normal View History

Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
########### decoration ###############
Declarative extension plugin for window decorations The generic QML components from Aurorae are split out into an own declarative plugin. In addition two new helper classes are added to this plugin: * A ColorHelper to map a few function of KColorSheme and making it possible to actually work with colors in QML. The need emerged from trying to port Plastik to QML which makes strong use of color shading. * A DecorationOptions class which is a wrapper around KWin's KDecorationOptions but in a more useable way for QML. The various options are provided as properties and the value of the properties changes automatically depending on whether the decoration is active or inactive. Aurorae itself is not yet adjusted to these changes, but it should also be adjusted as some of the options are currently exported in the factory and the factory is injected into the Aurorae QML decoration.
2012-07-27 08:03:22 +00:00
include_directories(
./lib
${CMAKE_CURRENT_BINARY_DIR}
${CMAKE_CURRENT_SOURCE_DIR}
)
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
set(kwin5_aurorae_PART_SRCS
Import of new Aurorae based on QGraphicsView and KDecoration instead of KCommonDecoration. It should support everything the old engine supported. Only known regression is the lack of tooltips. Now finally Aurorae is ready to get window tab support \o/ svn path=/trunk/KDE/kdebase/workspace/; revision=1114115
2010-04-12 19:28:58 +00:00
aurorae.cpp
[aurorae] Improve reading the border elements from C++ side The KWin::Borders element is provided by an extension plugin. The reason for that is to be able to use it from e.g. the kcm or Plasmate without needing to compile the code in. But this results in Aurorae itself not being able to access the element. The solution is to first load our decoration plugin and afterwards register the borders element again with the version compiled in from Aurorae. With that we can now read all borders and paddings without using properties. Also we could connect to change signals and have the borders and padding handling completely stateful. Might be an idea for extending the decoration library...
2014-06-18 07:06:49 +00:00
decorationoptions.cpp
Import of new Aurorae based on QGraphicsView and KDecoration instead of KCommonDecoration. It should support everything the old engine supported. Only known regression is the lack of tooltips. Now finally Aurorae is ready to get window tab support \o/ svn path=/trunk/KDE/kdebase/workspace/; revision=1114115
2010-04-12 19:28:58 +00:00
lib/auroraetheme.cpp
lib/themeconfig.cpp
)
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
add_library(kwin5_aurorae MODULE ${kwin5_aurorae_PART_SRCS})
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
target_link_libraries(kwin5_aurorae
KDecoration2::KDecoration
[kcmkwin/deco] Add configuration for decoration plugin/themes This brings back the configuration for decoration plugins. As a change to the old variant the configure button is moved into the list view together with the preview. It is enabled/disabled depending on data provided by the DecorationModel. For a plugin the DecorationModel queries for a boolean "kcmodule" key in the metadata. For a theme it invokes the slot hasConfiguration with the theme name which returns whether the theme provides configuration. The actual opening of the configuration is triggered from the PreviewBridge, which uses the existing KPluginFactory to load the KCModule. The decoration plugin must provide the keyword "kcmodule" for it. So far Aurorae is adjusted and provides configuration for the Plastik decoration. The interaction with the configuration module works, but the configuration itself for Plastik seems to be currently broken.
2014-12-05 12:44:16 +00:00
KF5::ConfigWidgets
KF5::I18n
Port to KF5 renaming changes
2013-12-11 20:41:47 +00:00
KF5::Service
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
KF5::WindowSystem
[aurorae] Use QtQuick2 instead of QtDeclarative Major transition to render using QtQuick 2. This means the actual rendering needs a QQuickWindow which we embed into a QWidget container. Not an optimal solution, deco API should offer to operate on QWindow. For non-composited the decoration gets rendered but for composited rendering the paint redirector is broken. There are no paint events on the main QWidget to intercept and thus the redirection doesn't work.
2013-10-02 08:04:10 +00:00
Qt5::Quick
[kcmkwin/deco] Add configuration for decoration plugin/themes This brings back the configuration for decoration plugins. As a change to the old variant the configure button is moved into the list view together with the preview. It is enabled/disabled depending on data provided by the DecorationModel. For a plugin the DecorationModel queries for a boolean "kcmodule" key in the metadata. For a theme it invokes the slot hasConfiguration with the theme name which returns whether the theme provides configuration. The actual opening of the configuration is triggered from the PreviewBridge, which uses the existing KPluginFactory to load the KCModule. The decoration plugin must provide the keyword "kcmodule" for it. So far Aurorae is adjusted and provides configuration for the Plastik decoration. The interaction with the configuration module works, but the configuration itself for Plastik seems to be currently broken.
2014-12-05 12:44:16 +00:00
Qt5::UiTools
Fix linking of Aurorae
2013-07-25 16:05:32 +00:00
)
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
install(TARGETS kwin5_aurorae DESTINATION ${PLUGIN_INSTALL_DIR}/org.kde.kdecoration2)
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
Declarative extension plugin for window decorations The generic QML components from Aurorae are split out into an own declarative plugin. In addition two new helper classes are added to this plugin: * A ColorHelper to map a few function of KColorSheme and making it possible to actually work with colors in QML. The need emerged from trying to port Plastik to QML which makes strong use of color shading. * A DecorationOptions class which is a wrapper around KWin's KDecorationOptions but in a more useable way for QML. The various options are provided as properties and the value of the properties changes automatically depending on whether the decoration is active or inactive. Aurorae itself is not yet adjusted to these changes, but it should also be adjusted as some of the options are currently exported in the factory and the factory is injected into the Aurorae QML decoration.
2012-07-27 08:03:22 +00:00
set(decoration_plugin_SRCS
decorationplugin.cpp
decorationoptions.cpp
colorhelper.cpp
)
add_library(decorationplugin SHARED ${decoration_plugin_SRCS})
Fix linking of Aurorae
2013-07-25 16:05:32 +00:00
target_link_libraries(decorationplugin
[aurorae] Change QML for themes to QtQuick 2 Needed for getting proper previews in the QtQuick 2 based kcm. Obviously this breaks Aurorae as Aurorae is not yet migrated to QtQuick 2. But there is no more broken than broken anyway.
2013-10-01 09:45:46 +00:00
Qt5::Quick
Initial port of Aurorae to KDecoration2 The port to KDecoration2 means quite some changes in the way how Aurorae works. First of all: the theme to load is passed to the Deocoration ctor and not searched for by Aurorae itself. The rendering mechanismn didn't change significantly yet. It's still rendering to an FBO and passing the image on. This needs some further work as KDecoration2 does not support the padding any more. So all themes using shadow are currently broken. Another big change is the way how the rendering scene is constructed and used. KDecoration2 doesn't want the the Decoration to be a native window. But for being able to render a QtQuick scene at all we need a QQuickWindow. Thus it creates a window parented to the decoration id, but not accepting any input event. Input is nowadays controlled from the outside: events are passed into the Decoration, so we don't want the QtQuick window intercepting events. In case of non-composited the normal FBO mechanism doesn't work and Aurorae just renders to the QQuickWindow directly. This could use some optimization in the decoration renderer in KWin core to not even try to perform the normal rendering. On the other hand it's probably too much a hassle for the use case. The rendering architecture might hopefully be improved with Qt 5.4 and the new QQuickRenderControl class. The QQuickWindow also exposes a problem for preview in the kdecoration-viewer and the future KCM: we don't want a different window, but best would be to get to the QML scene directly. A small hack is added to have the previewers set a "visualParent" which Aurorae uses to parent the QML scene to without the need to create a QQuickWindow.
2014-10-24 11:48:31 +00:00
KDecoration2::KDecoration
Port to KF5 renaming changes
2013-12-11 20:41:47 +00:00
KF5::ConfigWidgets
Fix linking of Aurorae
2013-07-25 16:05:32 +00:00
)
[aurorae] Change QML for themes to QtQuick 2 Needed for getting proper previews in the QtQuick 2 based kcm. Obviously this breaks Aurorae as Aurorae is not yet migrated to QtQuick 2. But there is no more broken than broken anyway.
2013-10-01 09:45:46 +00:00
install(TARGETS decorationplugin DESTINATION ${QML_INSTALL_DIR}/org/kde/kwin/decoration)
Declarative extension plugin for window decorations The generic QML components from Aurorae are split out into an own declarative plugin. In addition two new helper classes are added to this plugin: * A ColorHelper to map a few function of KColorSheme and making it possible to actually work with colors in QML. The need emerged from trying to port Plastik to QML which makes strong use of color shading. * A DecorationOptions class which is a wrapper around KWin's KDecorationOptions but in a more useable way for QML. The various options are provided as properties and the value of the properties changes automatically depending on whether the decoration is active or inactive. Aurorae itself is not yet adjusted to these changes, but it should also be adjusted as some of the options are currently exported in the factory and the factory is injected into the Aurorae QML decoration.
2012-07-27 08:03:22 +00:00
Initial import of Aurorae Kwin decoration theme engine. This theme engine uses SVG files to theme the decoration like the themes for Plasma desktop shell. svn path=/trunk/playground/artwork/aurorae/; revision=983819
2009-06-19 09:18:07 +00:00
########### install files ###############
GHNS support for Aurorae svn path=/trunk/KDE/kdebase/workspace/; revision=1007228
2009-08-05 10:37:24 +00:00
install( FILES aurorae.knsrc DESTINATION ${CONFIG_INSTALL_DIR} )
Aurorae goes QML What's working: * background for active and inactive decorations inclusive transitions * all buttons get loaded * transition between button states * all borders, paddings etc is working * mouse interaction with buttons and title area What's not yet working: * special maximize mode * mouse wheel on title area * window tabs * changing themes * crash resistence (currently a not compiling QML file crashes KWin badly) * window/blur mask (tricky - we need the alpha mask of the background SVG) What's going to be dropped: * special opaque mode * decoration position at left/right/bottom instead of top Why? Because nobody uses these features
2012-01-07 16:25:21 +00:00
install( FILES
qml/aurorae.qml
qml/AuroraeButton.qml
qml/AuroraeButtonGroup.qml
Better Maximized/Restore button Use just one button with the two variants embedded. Makes the state transitions more robust.
2012-01-10 18:26:59 +00:00
qml/AuroraeMaximizeButton.qml
Aurorae goes QML What's working: * background for active and inactive decorations inclusive transitions * all buttons get loaded * transition between button states * all borders, paddings etc is working * mouse interaction with buttons and title area What's not yet working: * special maximize mode * mouse wheel on title area * window tabs * changing themes * crash resistence (currently a not compiling QML file crashes KWin badly) * window/blur mask (tricky - we need the alpha mask of the background SVG) What's going to be dropped: * special opaque mode * decoration position at left/right/bottom instead of top Why? Because nobody uses these features
2012-01-07 16:25:21 +00:00
qml/Decoration.qml
qml/DecorationButton.qml
qml/MenuButton.qml
Support for Application Menu in Aurorae Aurorae supports in general the Aurorae button. So far themes are not able to style the button, instead the window's icon is used.
2012-12-27 09:29:13 +00:00
qml/AppMenuButton.qml
Aurorae goes QML What's working: * background for active and inactive decorations inclusive transitions * all buttons get loaded * transition between button states * all borders, paddings etc is working * mouse interaction with buttons and title area What's not yet working: * special maximize mode * mouse wheel on title area * window tabs * changing themes * crash resistence (currently a not compiling QML file crashes KWin badly) * window/blur mask (tricky - we need the alpha mask of the background SVG) What's going to be dropped: * special opaque mode * decoration position at left/right/bottom instead of top Why? Because nobody uses these features
2012-01-07 16:25:21 +00:00
DESTINATION ${DATA_INSTALL_DIR}/kwin/aurorae )
Declarative extension plugin for window decorations The generic QML components from Aurorae are split out into an own declarative plugin. In addition two new helper classes are added to this plugin: * A ColorHelper to map a few function of KColorSheme and making it possible to actually work with colors in QML. The need emerged from trying to port Plastik to QML which makes strong use of color shading. * A DecorationOptions class which is a wrapper around KWin's KDecorationOptions but in a more useable way for QML. The various options are provided as properties and the value of the properties changes automatically depending on whether the decoration is active or inactive. Aurorae itself is not yet adjusted to these changes, but it should also be adjusted as some of the options are currently exported in the factory and the factory is injected into the Aurorae QML decoration.
2012-07-27 08:03:22 +00:00
install( FILES
qml/Decoration.qml
qml/DecorationButton.qml
qml/MenuButton.qml
Support for Application Menu in Aurorae Aurorae supports in general the Aurorae button. So far themes are not able to style the button, instead the window's icon is used.
2012-12-27 09:29:13 +00:00
qml/AppMenuButton.qml
Declarative extension plugin for window decorations The generic QML components from Aurorae are split out into an own declarative plugin. In addition two new helper classes are added to this plugin: * A ColorHelper to map a few function of KColorSheme and making it possible to actually work with colors in QML. The need emerged from trying to port Plastik to QML which makes strong use of color shading. * A DecorationOptions class which is a wrapper around KWin's KDecorationOptions but in a more useable way for QML. The various options are provided as properties and the value of the properties changes automatically depending on whether the decoration is active or inactive. Aurorae itself is not yet adjusted to these changes, but it should also be adjusted as some of the options are currently exported in the factory and the factory is injected into the Aurorae QML decoration.
2012-07-27 08:03:22 +00:00
qml/ButtonGroup.qml
qml/qmldir
[aurorae] Change QML for themes to QtQuick 2 Needed for getting proper previews in the QtQuick 2 based kcm. Obviously this breaks Aurorae as Aurorae is not yet migrated to QtQuick 2. But there is no more broken than broken anyway.
2013-10-01 09:45:46 +00:00
DESTINATION ${QML_INSTALL_DIR}/org/kde/kwin/decoration )
Basic QML theme support in Aurorae Aurorae can load QML themes from Plasma package structures. Code not yet tested as there are no packages yet.
2012-07-22 15:35:18 +00:00
install( FILES kwindecoration.desktop DESTINATION ${SERVICETYPES_INSTALL_DIR} )
Reference in a new issue Copy permalink