Register shortcuts under wayland

lxqt / lxqt-globalkeys

Daemon used to register global keyboard shortcuts

https://lxqt.github.io

GNU Lesser General Public License v2.1

32 stars 35 forks source link

Register shortcuts under wayland #282

Open stefonarch opened 3 months ago

stefonarch commented 3 months ago

Expected Behavior

We can use lxqt-globalkeysd under wayland

Possible Solution

https://github.com/flatpak/xdg-desktop-portal/pull/711 No docs found here https://docs.flatpak.org/en/latest/portal-api-reference.html
No wlr protocol atm: https://wayland.app/protocols/
Plasma design for kwin: https://blog.martin-graesslin.com/blog/2015/06/global-shortcut-handling-in-a-plasma-wayland-session/

Also for other global shortcut systems to work with KWin it’s needed to port them to use KGlobalAccel internally when running in a Plasma/Wayland session (that’s also a good idea for X11 sessions as KGlobalAccel can provide additional features like checking whether the key is already taken by another process).
Wrapper for writing to different compositors configs (workaround)

tsujan commented 3 months ago

lxqt-globalkeys heavily depends on X11. A totally different code might be needed.

As you already know better than I do, Wayland WMs (and especially, labwc) come with their own shortcut handling because, unlike the case of X11, they can't be just WMs.

redtide commented 2 months ago

Use backends there too? Basically lxqt global keys becomes a gui frontend like an ObKeys on labwc etc, moving the current code to a x11 backend.

marcusbritanicus commented 2 months ago

@redtide while this is a reasonable suggestion, there isn't a common protocol which can be used for a generic backend. Do you know of any wm that allows registration of arbitrary key-bindings? We may have that support in Wayfire using its IPC mechanism. But that's still under development, and isn't released yet, I think.

redtide commented 2 months ago

ATM only OB and Labwc but it doesn't matter, what I'm saying is to make GlobalKeys like a wrapper/frontend that can adapts to various implementations. One could be also the portal mentioned in the OP.

marcusbritanicus commented 2 months ago

The thing with the portal is that it still requires support from the compositor. The portal will contain the code that will communicate with the compositor. Currently, we do not have any means of communication - typically, this is via a protocol (wayland/wlroots/private) or some IPC mechanism.