Feature #985
Updated by Hammel about 1 year ago
There is a cairo keyboard embedded in the old dialer app for the custom hardware Xeon project. This might still be used, perhaps as a library. Or I could try using "matchbox-keyboard":https://github.com/Xlab/matchbox-keyboard and fix up the display. Or I can try more sophisticated X/Wayland on-screen keyboards, like virtboard or squeekboard. But I think the idea of having to use dbus for a keyboard seems odd. I don't want the keyboard to get keyboard focus either. But I need a general purpose solution that I can re-use across apps. See * https://github.com/mwilliams03/matchbox-keyboard or https://github.com/xlab/matchbox-keyboard ** "Matchbox keyboard toggler":https://gist.github.com/xlab/3104348 * https://gitlab.com/cubocore/coreapps/corekeyboard * https://source.puri.sm/Librem5/squeekboard * https://source.puri.sm/Librem5/virtboard * https://github.com/maliit/keyboard * https://github.com/KDE/kvkbd * https://www.semicomplete.com/projects/xdotool/ - fake keyboard input via XTEST. Comes with a library. There is also bui-keyboard (cdtools buik), bui-keyboard, the Matchbox keyboard build I tested long ago. This could be embedded in a GTK+2 app. There are examples of how to do this. If nothing else, this could be a template for writing my own keyboard app. And then there is bui-fakekey (cdtools buif) that provides a library for simulating keypresses. With the latter I can capture a touch on a Cairo button and simulate the keypress in another widget.