• DonutsRMeh@lemmy.world
    2·
    2 hours ago

    “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.

  • qaz@lemmy.worldEnglish
    2·
    4 hours ago

    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.

  • Coelacanthus@lemmy.kde.social
    1·
    6 hours ago

    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.

  • thevoidzero@lemmy.world
    5·
    2 days ago

    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.

    • Björn Tantau@swg-empire.de
      4·
      2 days ago

      But it works.

      Wanted to install OpenSUSE Tumbleweed with KDE as desktop on my Steam Deck without getting a keyboard. Had to use the Gnome Live image because it’s the only one with a working keyboard.

  • pak0st@fosstodon.org
    11·
    24 hours ago

    @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 protocol  
ASSERT failure in Q\_UNREACHABLE(): "Q\_UNREACHABLE was reached", file /home/pak0stpc/Projects/plasma-keyboard/src/main.cpp, line 292  
Aborted (core dumped) QT\_IM\_MODULES=qtvirutalkeyboard ./bin/plasma-keyboard

    I would like to give it a shot on my system

  • BlessedDog@lemmy.world
    1·
    1 day ago

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

  • Björn Tantau@swg-empire.de
    3·
    2 days ago

    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.

  • thevoidzero@lemmy.world
    3·
    2 days ago

    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!
    • DaPorkchop_@lemmy.ml
      5·
      2 days ago

      In the future, you can generally solve these sorts of build errors by just installing the development package for whatever library is missing. On Debian-based systems, that would be something along the lines of sudo apt install libecm<tab><tab> see what appears, choose one which looks reasonable with -dev suffix

      • thevoidzero@lemmy.world
        3·
        2 days ago

        Thank you.

        In this case installing ecm-tools (I use arch) didn’t fix it. That was the first thing I tried before making an issue.

        It needed extra packages for cmake (refer to the issue for details)

  • woelkchen@lemmy.world
    51·
    2 days ago

    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.