Why work on something quietly when you can work on it loudly?

This will be great for Steam Deck.

@kde@floss.social @kde@lemmy.kde.social That's great! Thank you, KDE team! I need this on my laptop that can transform into a tablet and back in runtime.

The Gnome OSK is actually so terrible.

Idk why all on screen keyboard come without tab key in plasma. I have a laptop while in a tablet mode I can't use terminal at all because there's no tab key.

As long as it has modifier and F keys, accepts mouse input and is manually toggleable I'm happy. Bonus points if I can configure it to show those and number keys per default.

@kde@floss.social @kde@lemmy.kde.social can you rebuild swype, the only phone keyboard that ever worked worth a damn?

It's just a Plasma skin for Qt Virtual Keyboard. Not that this is bad but KDE developers are co-maintainers of Maliit and ended up contributing very little.

@kde@floss.social @kde@lemmy.kde.social thanks!I wouldnt mind funding a great onscreen-keyboard, especially with special keys that make it actually usable (alt, ctrl, shift etc.).

Let's hope it works a bit better with the floating plasma dock than Maliit. Having some weird graphical issues with my current setup.

Will it work on X? xd

Will it work well with existed IME like Fcitx5? Or I can choose only one of them?

I see Qt Virtual Keyboard has their own InputMethod implementations, but I think it's not a good idea to re-invent a new IME when there is no obvious advantage, because InputMethod is not a simple thing in some languages like Chinese and Japanese.

For example, libime, the core algorithm library of fcitx5-chinese-addons uses 47k SLOC to implement a good pinyin input method algorithm, even not count the Trigram language model, which is around 30MiB.

As a comparison, the pinyin algorithm of Qt Virtual Keyboard (it seems come from deprecated AOSP's PinyinIME) uses only 8k SLOC. And PinyinIME was give up by AOSP since 2014, it never updates since that time (and no algorithm update since 2009). At 2018, Qt pull it into Qt Virtual Keyboard and never do actual algorithm optimization. So it has fallen away from the time.

Edit: issue made and fixed https://invent.kde.org/plasma/plasma-keyboard/-/issues/12

Looks like I need kde-gitlab account fpr making issues.

I couldn't compile it,

cmake ..

-- The C compiler identification is GNU 15.1.1
-- The CXX compiler identification is GNU 15.1.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (find_package):
  By not providing "FindECM.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "ECM", but
  CMake did not find one.

  Could not find a package configuration file provided by "ECM" (requested
  version 6.0.0) with any of the following names:

    ECMConfig.cmake
    ecm-config.cmake

  Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR"
  to a directory containing one of the above files.  If "ECM" provides a
  separate development package or SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!

This is a great initiative! I tried plasma on a tablet like device a while ago and the keyboard was one of the main issues holding it back.

"we care about your input" is 180 from gnome's "you're an idiot, and we know what's best for you". I think kde did this on purpose 😂. That's why I never use anything else.

#Plasma-OSK-has-been-a-mess-since-forever #FINALLY-:4

@kde@floss.social @kde@lemmy.kde.social hmm... how to resolve this error?QT_IM_MODULES=qtvirutalkeyboard ./bin/plasma-keyboard Failed to initialize input panel-shell integration, possibly because compositor does not support the layer-shell protocolASSERT failure in Q_UNREACHABLE(): "Q_UNREACHABLE was reached", file /home/pak0stpc/Projects/plasma-keyboard/src/main.cpp, line 292Aborted (core dumped) QT_IM_MODULES=qtvirutalkeyboard ./bin/plasma-keyboardI would like to give it a shot on my system

Good to know, a fully working + visually ok on screen keyboard is one of the few things I actually miss after my switch from windows. Most I've tried have issues, and even my current "best" xvkbd has some issues (plus it's ugly).

I saw this! Been using this on my laptop, a Latitude 2-in-1, testing over the one I was using before. So far so good! Nice to see them working on their own, not just having the API for it. Having to dig around to figure out how to install one for it sucked.