Review Request 121856: KWindowSystem import for KDeclarative

Thomas Lübking thomas.luebking at gmail.com
Thu Feb 19 14:11:04 UTC 2015


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121856/#review76295
-----------------------------------------------------------


I'd say that the window related functions that are not already supported (raise, lower, desktop, ...) should be added to the QML Window type (oo-style + declarative) and only the actual WindowSystem / WindowManager related stuff (current desktop, compositing state, ...) should be done in an extra component (to query the WM state)


src/qmlcontrols/kwindowsystemplugin/kwindowsystemproxy.h
<https://git.reviewboard.kde.org/r/121856/#comment52585>

    Window.alert?



src/qmlcontrols/kwindowsystemplugin/kwindowsystemproxy.h
<https://git.reviewboard.kde.org/r/121856/#comment52586>

    Window.visibililty?



src/qmlcontrols/kwindowsystemplugin/kwindowsystemproxy.h
<https://git.reviewboard.kde.org/r/121856/#comment52587>

    windowFromId reasoning applies here as well


- Thomas Lübking


On Jan. 5, 2015, 10:49 vorm., Kai Uwe Broulik wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/121856/
> -----------------------------------------------------------
> 
> (Updated Jan. 5, 2015, 10:49 vorm.)
> 
> 
> Review request for kwin and Plasma.
> 
> 
> Repository: kdeclarative
> 
> 
> Description
> -------
> 
> This is a thin proxy around KWindowSystem exposing most of its methods to qml via KWindowSystem item in an org.kde.kwindowsystem import.
> 
> It uses QWindow instead of WId parameters so you can just pass a qml Item, such as a Plasma Dialog as parameter for ease of use (and so you cannot mess with others windows without effort, also I don't know what "WId" would translate to anyway). It omits all those methods that return WId/QWindow as I don't know how expensive QWindow::fromWinId is or who takes ownership of it. We need to decide which methods make sense in this import.
> 
> Methods that have signals and don't take parameters are turned into full-fledged properties (like currentDesktop, numberOfDesktops, etc) and the rest stays Q_INVOKABLE.
> 
> 
> Diffs
> -----
> 
>   src/qmlcontrols/kwindowsystemplugin/qmldir PRE-CREATION 
>   src/qmlcontrols/kwindowsystemplugin/kwindowsystemproxy.cpp PRE-CREATION 
>   src/qmlcontrols/CMakeLists.txt 39c39a5 
>   src/qmlcontrols/kwindowsystemplugin/CMakeLists.txt PRE-CREATION 
>   src/qmlcontrols/kwindowsystemplugin/kwindowsystemplugin.h PRE-CREATION 
>   src/qmlcontrols/kwindowsystemplugin/kwindowsystemplugin.cpp PRE-CREATION 
>   src/qmlcontrols/kwindowsystemplugin/kwindowsystemproxy.h PRE-CREATION 
> 
> Diff: https://git.reviewboard.kde.org/r/121856/diff/
> 
> 
> Testing
> -------
> 
> The properties work and change accordingly (compositing active signal doesn't seem to be emitted by KWindowSystem in the first place, at least Ctrl+Shift+F12 doesn't make it change), the forceActivateWindow method works for Review 121807
> 
> 
> Thanks,
> 
> Kai Uwe Broulik
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20150219/c53036aa/attachment-0001.html>


More information about the Plasma-devel mailing list