This was a time ago, but I don’t think I tried any of them out, I think I just went on a research spree to collect all that I could find.
As of my personal use, I’ve only managed to get the maliit keyboard working with plasma, but it is sadly lacking, and the codebase is not small, so hacking on it was daunting.
I will say, the protocol issue doesn’t seem too bad, with virtual-keyboard-unstable-v1.xml, although being listed as external, having pretty good compositor support outside of GNOME and Plasma, so perhaps it could/will be merged into the main wayland-protocols in due time, and that would simplify the requirements for the people developing the virtual keyboard applications.
That being said, I think that the current ecosystem of virtual keyboards is quite lacking, and there definitely needs to be some sort of specification or other form of standardisation made to help developers, but I’m not sure how one could go about that.
Running it on Arch, Plasma 6 gives me:
** (squeekboard:79749): ERROR **: 14:09:39.770: No virtual keyboard manager Wayland global available.
[1] 79749 trace trap (core dumped) squeekboard
Seems that it’s looking for a wayland protocol that isn’t supported in Plasma, and given that Arch has one of Squeekboard’s deps being the GNOME desktop, I’d say that’s probably the case.
(apologies for the reply spam)
Edit: Just tried to build Squeekboard, and meson fails with:
Run-time dependency gnome-desktop-3.0 found: NO (tried pkgconfig and cmake)
So it’s not just arch wanting gnome-desktop, it seems to be a hard-coded dependancy.
I’ll try and hack on it to try and get it running under Plasma, but no promises.
Edit 2: it’s very hard-coded to be basically just GNOME-only unfortunately. It wants GNOME deps, GNOME Dbus sessions, just all the GNOME things, so it may be out of the question.
Too busy making sure your tablet pen buttons can be interchangable I guess.
Its hard to not be bitter about this when its such an accessibility nightmare.
Developing efforts dont contradict each other
KDE is not a company with people that could do anything but some management doesnt want them to.
It is literally all volunteers
“Fixing the elevator is boring so we removed it. Take the stairs, cripple.”
I dont see how this is a reasonable comment
The truth hurts.
No, annoying and harrassing comments hurt.
Bitter and spiteful comments are the opposite of helpful: they reduce the motivation of any volunteers who might be interested in working on the issue. Please keep comments positive, useful, helpful, actionable, or interesting, thanks.
Again, we know it’s bad. We’re asking for a bit of patience as we scope out a solution.
A probably stupid question for which I apologise to the whole community. To write a keyboard on Plasma 6, what languages should I know how to programme in, bearing in mind that I am using Wayland?
From what I see it is available as a flatpak as well for those that use flatpak.
Qt has bindings to C++ and Python. There are also Rust bindings but not very good ones afaik.
Python would be the best language if you want contributions.
I am not going to sit around for another several years listening to you guys whine about how people’s inability to use a machine because you r e m o v e d accessibility features on account of fixing them being “oh but its so boring ):”.
I would rather risk a suspension or outright ban or whatever kicking up a stink about this because of just how utterly ridiculous some of the replies/reasons/excuses I’ve seen over the years.
It takes zero effort to evade the “hey, accessibility sucks are you fixing that” yet you all decided to make it personal by outright stating that its too boring to work on and “uwu sad truth”.
If we have to swallow the sad truth of being too boring to help then you have to live with the consequences of that as well.
“I would prefer to be a jerk and get banned!” is an awfully strange position to take, and there is literally no benefit to anyone. I see one of the mods gave you what you were looking for. 
Update: with the help of some of the people over at #kde-input I have put together a bit of a resource for developers looking to help with this: GitHub - Hoverth/wayland-virtual-keyboards: Useful resources on making OSKs on Wayland (do note that it isn’t KDE exclusive!)
I have as well started an attempt at extending Aleix Pol’s QVK, that can be found [GitHub link] here, which just needs people who are good with QML to help out, as I’m stumbling around a bit I feel 