yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/kcmkwin/kwincompositing/qml/Effect.qml

217 lines
9.4 KiB
QML
Raw Normal View History

Fix license
2013-06-25 14:26:54 +00:00
/**************************************************************************
* KWin - the KDE window manager *
* This file is part of the KDE project. *
* *
* Copyright (C) 2013 Antonis Tsiapaliokas <kok3rs@gmail.com> *
* *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License as published by *
* the Free Software Foundation; either version 2 of the License, or *
* (at your option) any later version. *
* *
* This program is distributed in the hope that it will be useful, *
* but WITHOUT ANY WARRANTY; without even the implied warranty of *
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
* GNU General Public License for more details. *
* *
* You should have received a copy of the GNU General Public License *
* along with this program. If not, see <http://www.gnu.org/licenses/>. *
**************************************************************************/
Initial commit
2013-06-25 14:07:48 +00:00
import QtQuick 2.1
import QtQuick.Controls 1.0
import QtQuick.Layouts 1.0
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
import org.kde.kwin.kwincompositing 1.0
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
import QtMultimedia 5.0 as Multimedia
import org.kde.qtextracomponents 2.0 as QtExtra
Initial commit
2013-06-25 14:07:48 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Item {
id: item
width: parent.width
height: 40
signal changed()
property alias checked: effectStatusCheckBox.checked
Add ExclusiveGroup support to the checkboxes of the ListView. Only ONE of the following effects can be active at the same time. *kwin4_effect_slideEnabled *kwin4_effect_cubeslideEnabled *kwin4_effect_fadedesktopEnabled
2013-08-19 16:50:01 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Rectangle {
id: background
color: item.ListView.isCurrentItem ? effectView.backgroundActiveColor : index % 2 ? effectView.backgroundNormalColor : effectView.backgroundAlternateColor
anchors.fill : parent
Initial commit
2013-06-25 14:07:48 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
RowLayout {
id: rowEffect
anchors.fill: parent
CheckBox {
function isDesktopSwitching() {
if (model.ServiceNameRole == "kwin4_effect_slide") {
return true;
} else if (model.ServiceNameRole == "kwin4_effect_fadedesktop") {
return true;
} else if (model.ServiceNameRole == "kwin4_effect_cubeslide") {
return true;
} else {
return false;
Initial commit
2013-06-25 14:07:48 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
}
function isWindowManagementEnabled() {
if (model.ServiceNameRole == "kwin4_effect_dialogparent") {
windowManagementEnabled = effectStatusCheckBox.checked;
return windowManagementEnabled = effectStatusCheckBox.checked && windowManagementEnabled;
} else if (model.ServiceNameRole == "kwin4_effect_desktopgrid") {
windowManagementEnabled = effectStatusCheckBox.checked;
return windowManagementEnabled = effectStatusCheckBox.checked && windowManagementEnabled;
} else if (model.ServiceNameRole == "kwin4_effect_presentwindows") {
windowManagementEnabled = effectStatusCheckBox.checked;
return windowManagementEnabled = effectStatusCheckBox.checked && windowManagementEnabled;
Buttons are enable only when they have something to do
2013-08-02 13:21:33 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
return windowManagementEnabled;
Initial commit
2013-06-25 14:07:48 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
id: effectStatusCheckBox
property bool windowManagementEnabled;
checked: model.EffectStatusRole
exclusiveGroup: isDesktopSwitching() ? desktopSwitching : null
onCheckedChanged: item.changed()
Implement the KCModule::defaults
2013-12-02 14:59:31 +00:00
Connections {
target: searchModel
onDataChanged: {
effectStatusCheckBox.checked = model.EffectStatusRole;
}
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
}
Add an about button for the author and the license of the effect
2013-07-31 08:47:15 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Item {
id: effectItem
width: effectView.width - effectStatusCheckBox.width - aboutButton.width - configureButton.width
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
height: item.height
anchors.top: rowEffect.top
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
anchors.left: effectStatusCheckBox.right
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
MouseArea {
id: area
width: effectView.width - effectStatusCheckBox.width
height: effectView.height
onClicked: {
effectView.currentIndex = index;
}
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Column {
id: col
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
height: parent.height
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Text {
text: model.NameRole
}
Text {
id: desc
function wrapDescription() {
if (wrapMode == Text.NoWrap) {
wrapMode = Text.WordWrap;
elide = Text.ElideNone;
} else {
wrapMode = Text.NoWrap;
elide = Text.ElideRight;
Add an about button for the author and the license of the effect
2013-07-31 08:47:15 +00:00
}
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
text: model.DescriptionRole
width: effectView.width - 100
elide: Text.ElideRight
Initial commit
2013-06-25 14:07:48 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Item {
id:aboutItem
anchors.top: desc.bottom
anchors.topMargin: 20
visible: false
Text {
text: "Author: " + model.AuthorNameRole + "\n" + "License: " + model.LicenseRole
font.bold: true
Initial commit
2013-06-25 14:07:48 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
PropertyAnimation {id: animationAbout; target: aboutItem; property: "visible"; to: !aboutItem.visible}
PropertyAnimation {id: animationAboutSpacing; target: item; property: "height"; to: item.height == 40 ? item.height + 100 : 40}
Initial commit
2013-06-25 14:07:48 +00:00
}
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
Multimedia.Video {
id: videoItem
function showHide() {
replayButton.visible = false;
if (videoItem.visible === true) {
videoItem.stop();
videoItem.visible = false;
// TODO: this should be done in a better way
item.height = item.height - 400;
} else {
videoItem.visible = true;
videoItem.play();
item.height = item.height + 400;
}
}
autoLoad: false
source: model.VideoRole
visible: false
width: 400
height: 400
anchors.bottom: parent.bottom
MouseArea {
// it's a mouse area with icon inside to not have an ugly button background
id: replayButton
visible: false
anchors.fill: parent
onClicked: {
replayButton.visible = false;
videoItem.play();
}
QtExtra.QIconItem {
id: replayIcon
anchors.centerIn: parent
width: 16
height: 16
icon: "media-playback-start"
}
Connections {
target: videoItem
onStopped: {
replayButton.visible = true
}
}
}
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
}
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
}
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
Integrate video into the UI A video button is shown if the model provides an url for a video. If the button is pressed the video element is added in a similar way to the aboutInfo and starts the video directly. Once the playback stopped a play again button is shown. If one clicks the video button again, the video gets hidden. Room for improvement: * add a button to open in external player * ensure video is centered correctly in the list view
2013-12-03 08:24:53 +00:00
Button {
id: videoButton
anchors.right: effectConfig.effectUiConfigExists(model.ServiceNameRole) ? configureButton.left : aboutButton.left
visible: model.VideoRole.toString() !== ""
iconName: "video"
onClicked: videoItem.showHide()
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Button {
id: configureButton
anchors.right: aboutButton.left
visible: effectConfig.effectUiConfigExists(model.ServiceNameRole)
enabled: effectStatusCheckBox.checked
iconName: "configure"
onClicked: {
effectConfig.openConfig(model.NameRole);
Add an about button for the author and the license of the effect
2013-07-31 08:47:15 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
}
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
Button {
id: aboutButton
anchors.right: parent.right
iconName: "dialog-information"
onClicked: {
animationAbout.running = true;
animationAboutSpacing.running = true;
desc.wrapDescription();
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
}
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
}
EffectConfig {
id: effectConfig
}
Load the configuration UI for the Effects
2013-08-01 16:20:37 +00:00
Drop the Apply button from the EffectView We have an Apply and OK button in the KCModule, so we don't need one in the view. A change signal is introduced and passed from the individual items upwards, so that we can connect to it from the C++ side.
2013-12-02 10:22:57 +00:00
} //end Row
} //end Rectangle
} //end item
Initial commit
2013-06-25 14:07:48 +00:00
Reference in a new issue Copy permalink