OSK infrastructure

[leolost2605]

Based on #2793

Note: To test this you need to start an app with GTK_IM_MODULE=wayland

Todo:

• There seems to be a bug where the osk sometimes doesn't get enabled?

Daemon:

• Popup keys
• icons for special buttons
• Language selection -> follow up
• Emoji selection -> follow up
• IBus suggestions -> follow up

[leolost2605]

This should be enough infrastructure for an initial osk:

Kooha-2026-03-26-18-20-52.mp4

@danirabbit @desiderantes any opinions/suggestions on design etc.? (I pinged you because I saw you talked about OSK in discord). If you have some ideas regarding structure/design/etc. that would be great!

If not I'll probably do it like GNOME does it so that we can also reuse their file format for keyboard layouts 🤷

[danirabbit]

@leolost2605 being able to re-use layouts from an existing OSK sounds like a good idea to me! We can always revisit if for some reason it's too restrictive, but otherwise I like doing less work 😜

[desiderantes]

There's some wayland protocols for virtual keyboards that might be of interest ( I experimented implementing them, because I was playing with basing the logic on the Android keyboard). Mainly the one for virtual keyboard and maybe input v2

[leolost2605]

There's some wayland protocols for virtual keyboards that might be of interest ( I experimented implementing them, because I was playing with basing the logic on the Android keyboard). Mainly the one for virtual keyboard and maybe input v2

Thanks for the input! I don't think input v2 applies here. Also we have usually done any interaction with the compositor that doesn't involve actual surfaces via dbus so I would keep doing it via dbus in this case too.