kwin/qml/CMakeLists.txt

install( DIRECTORY outline/plasma   DESTINATION ${DATA_INSTALL_DIR}/${KWIN_NAME}/outline )
install( DIRECTORY virtualkeyboard   DESTINATION ${DATA_INSTALL_DIR}/${KWIN_NAME} )
[kwin] Provide composited outline as QML instead of hand drawn FrameSvg In order to get all our UI being written in QML, the Outline for compositing is ported to QtQuick. It creates a QQmlContext and QQmlComponent and loads the (currently hardcoded) qml file. The context gets to properties exported: outline. The outline property allows the qml to get the geometry it should use. The QQmlEngine is used from Scripting thus all general scripting properties are exported (e.g. workspace). The qml script is expected to create a QQuickWindow as it's root item and style it. The qml file is stored in a new qml subdirectory. The idea is that each of the qml types we have gets an own directory there and for each implementation there should be a further subdirectory. Thus we have outline/plasma/ with outline being the type and plasma being the implementation. But at the moment the script location is still hardcoded. REVIEW: 116123 2014-02-27 14:25:03 +00:00			`install( DIRECTORY outline/plasma DESTINATION ${DATA_INSTALL_DIR}/${KWIN_NAME}/outline )`
Integrate QtVirtualKeyboard into KWin/Wayland Summary: The idea is to have KWin provide a virtual keyboard. To support this KWin uses the QT_IM_MODULE qtvirtualkeyboard and makes sure that the QPA plugin loads it. KWin has a new class VirtualKeyboard which acts as the focus object and the "proxy" for input methods. The QPA plugin ensures that this is the focusObject, so that all input method related events are sent to this class. From there it will be possible to delegate to other applications through the Wayland interfaces. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D1638 2016-04-29 13:05:03 +00:00			`install( DIRECTORY virtualkeyboard DESTINATION ${DATA_INSTALL_DIR}/${KWIN_NAME} )`