Open emersion opened 5 years ago
Hey, is there any plan to support this feature?
Kdeconnect recently merged a feature that'll make the remote input plugin compatible with Wayland and it relies on RemoteDesktop. See https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/501. This will make the Kdeconnect smartphone app able to control the desktop's cursor & keyboard remotely, which is one of the few things I've been missing since I made the transition to Wayland and I'm sure I'm not the only one.
I'd be ok with trying to work on a PR but I'd need some guidance as to what to do and where, as I'm not familiar at all with this project and xdg-desktop-portal's internals in general.
Feel free to come and ask questions on IRC. It all boils down to implementing the D-Bus interface (this repo has some example code, mako too) by using the Wayland protocols.
Hey, is there any plan to support this feature?
Kdeconnect recently merged a feature that'll make the remote input plugin compatible with Wayland and it relies on RemoteDesktop. See https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/501. This will make the Kdeconnect smartphone app able to control the desktop's cursor & keyboard remotely, which is one of the few things I've been missing since I made the transition to Wayland and I'm sure I'm not the only one.
I'd be ok with trying to work on a PR but I'd need some guidance as to what to do and where, as I'm not familiar at all with this project and xdg-desktop-portal's internals in general.
What do you mean by "it relies on remote desktop"? and Is it working now?
Hey, is there any plan to support this feature? Kdeconnect recently merged a feature that'll make the remote input plugin compatible with Wayland and it relies on RemoteDesktop. See https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/501. This will make the Kdeconnect smartphone app able to control the desktop's cursor & keyboard remotely, which is one of the few things I've been missing since I made the transition to Wayland and I'm sure I'm not the only one. I'd be ok with trying to work on a PR but I'd need some guidance as to what to do and where, as I'm not familiar at all with this project and xdg-desktop-portal's internals in general.
What do you mean by "it relies on remote desktop"? and Is it working now?
The KDE connect client allows you to use your phone as keyboard / touchpad for your KDE connect server. Running the server under sway currently only supports some of KDE connect's features (volume and multimedia controls work) while the remote input would require support for the RemoteDesktop extension in the wlr portal.
Hey, is there any plan to support this feature? Kdeconnect recently merged a feature that'll make the remote input plugin compatible with Wayland and it relies on RemoteDesktop. See https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/501. This will make the Kdeconnect smartphone app able to control the desktop's cursor & keyboard remotely, which is one of the few things I've been missing since I made the transition to Wayland and I'm sure I'm not the only one. I'd be ok with trying to work on a PR but I'd need some guidance as to what to do and where, as I'm not familiar at all with this project and xdg-desktop-portal's internals in general.
What do you mean by "it relies on remote desktop"? and Is it working now?
The KDE connect client allows you to use your phone as keyboard / touchpad for your KDE connect server. Running the server under sway currently only supports some of KDE connect's features (volume and multimedia controls work) while the remote input would require support for the RemoteDesktop extension in the wlr portal.
So how we can do that?
As @emersion wrote,
Feel free to come and ask questions on IRC. It all boils down to implementing the D-Bus interface (this repo has some example code, mako too) by using the Wayland protocols.
See https://github.com/flatpak/xdg-desktop-portal/blob/master/data/org.freedesktop.impl.portal.RemoteDesktop.xml
We can use the wlroots virtual-keyboard and virtual-pointer protocols.