Maliit

Maliit framework Fix paths in maliit-defines.prf Use compose input plugin fallback only if key redirection is disabled Remove leftover code from Qt 4 times Enable installing unit tests again Remove legacy unused Maemo-specific code Use ... [More] QLoggingCategory for logging Fix application orientation angle back to clockwise Add the Mir input panel window type flag Use CMAKE_INSTALL_FULL_* paths in pkgconfig files Remove the unused and unnecessary gtk3 wayland input context plugin Remove unused and useless install target Maliit keyboard Add CI build rule to build on KDE Neon Remove unused window flag setting code Replace remaining context properties with singletons Remove unused and useless install target Fix builds without Pinyin Fix the build of unit tests and enable them by default Fix a possible undefined error in CharKey Improve the PhoneNumber keyboard layout Fix the settings URL for Plasma Mobile kcm renaming Use new syntax for Connections components Rely on QQC2 styles insted of an internal themes implementation Where can I get it? framework: maliit-framework-2.3.0.tar.gz keyboard: maliit-keyboard-2.3.0.tar.gz What is it? Maliit provides a flexible and cross-platform input method framework. It has a plugin-based client-server architecture where applications act as clients and communicate with the Maliit server via input context plugins. Maliit is an open source framework (LGPL 2.1 or later) and an open source on-screen keyboard (LGPL 3.0 only). Maliit is being used by KDE for Plasma, LG for webOS, Ubuntu Touch, LuneOS, Sailfish OS, and likely others. Visit maliit.github.io for more information about the project. Call for contributions Maliit’s website could benefit from a little love. Some of the information is no longer up to date. If anybody out there has some time to spare to fix it up a little bit, hop to github.com/maliit/maliit.github.io and send us a pull request. Should anybody with some influence at Canonical happen to read this announcement: We have nothing against the LGPL 3.0 but we’d like some consistency in our licensing. Maliit Keyboard was originally BSD-licensed but Canonical code from 2014 until 2017 is licensed under LGPL-3.0-only. If Canonical could send us a PR replacing the LGPL 3.0 headers with BSD ones, we’d appreciate it. We currently lack the manpower to crawl through various forks of Maliit Framework and Keyboard. We’re aware of them and we totally support the right of anybody to fork all Free Software code but not always is new code in those forks specific to custom implementations. A helping hand or two that ports improvements useful for our upstream code would, again, be very appreciated. [Less]

Maliit framework Re-show the keyboard on Wayland surrounding text changes Maliit keyboard Fix install issue in 2.2.1 tarball Remove the legacy CC-BY 3.0 licensed artwork Simplify ActionsToolbar by removing need for states Visual ... [More] spacing improvements for Keyboard and WordRibbon Add a visible separator between word suggestions Select a minimum width for word suggestion labels Make word suggestion font size proportional to WordRibbon height Hide WordRibbon when in cursor mode Make wordRibbon height proportional to Keyboard keys Only load emoji keyboard QML when state is EMOJI Fix typo in internal API (@sunweaver) Adjust glib deprecation fix to work with glib < 2.68 Update Italian translation Ensure all icon names are corrrect and using symbolic variants Fix some typos in QML imports Make sursor mode available for Japanese plugin Enable use of anthy-unicode instead of anthy Where can I get it? framework: maliit-framework-2.2.1.tar.gz keyboard: maliit-keyboard-2.2.1.1.tar.gz What is it? Maliit provides a flexible and cross-platform input method framework. It has a plugin-based client-server architecture where applications act as clients and communicate with the Maliit server via input context plugins. Maliit is an open source framework (LGPL 2.1 or later) and an open source on-screen keyboard (LGPL 3.0 only). Maliit is being used by KDE for Plasma, LG for webOS, Ubuntu Touch, LuneOS, Sailfish OS, and likely others. Visit maliit.github.io for more information about the project. Call for contributions Maliit’s website could benefit from a little love. Some of the information is no longer up to date. If anybody out there has some time to spare to fix it up a little bit, hop to github.com/maliit/maliit.github.io and send us a pull request. Should anybody with some influence at Canonical happen to read this announcement: We have nothing against the LGPL 3.0 but we’d like some consistency in our licensing. Maliit Keyboard was originally BSD-licensed but Canonical code from 2014 until 2017 is licensed under LGPL-3.0-only. If Canonical could send us a PR replacing the LGPL 3.0 headers with BSD ones, we’d appreciate it. We currently lack the manpower to crawl through various forks of Maliit Framework and Keyboard. We’re aware of them and we totally support the right of anybody to fork all Free Software code but not always is new code in those forks specific to custom implementations. A helping hand or two that ports improvements useful for our upstream code would, again, be very appreciated. [Less]

Maliit framework Fix sending of modifiers and keysyms on Wayland Fix Qt and glib deprecation warnings Update the Doxyfile Use text-input-unstable-v2 protocol Enable GitHub Actions CI and fix tests Fix build failure when XCB is disabled ... [More] Lower CMake requirement to 3.5 Maliit keyboard Revert to simpler method of word engine plugin loading Improved layout switching behavior to cycle through all enabled languages Handle invalid values being set for active and enabled languages Remove previous-language setting Support for disabling keyboard hide and unhide animations Integrate emoji layout into main keyboard Fix the default hunspell dictionary path Fix Qt and glib deprecation warnings during compilation Add ẞ and missing currency symbols to German keyboard Fix build with hunspell disabled Synchronize changes from Lomiri keyboard fork Selection mode available when in cursor mode now Toolbar in cursor mode for undo/redo/select all and cut/copy/paste Belarusian layout Bulgarian layout English (Dvorak) layout French (Swiss) layout Lithuanian layout Macedonian layout Thai layout Turkish layout Fix compilation with presage enabled on c++17 default compilers Enable translations support Set haptic feedback duration to 100ms and intensity to 0.5 Add haptic feedback to spacebar Use the correct kcm name for settings in Plasma Mobile Where can I get it? framework: maliit-framework-2.2.0.tar.gz keyboard: maliit-keyboard-2.2.0.tar.gz What is it? Maliit provides a flexible and cross-platform input method framework. It has a plugin-based client-server architecture where applications act as clients and communicate with the Maliit server via input context plugins. Maliit is an open source framework (LGPL 2.1 or later) and an open source on-screen keyboard (LGPL 3.0 only). Maliit is being used by KDE for Plasma, LG for webOS, Ubuntu Touch, LuneOS, Sailfish OS, and likely others. Visit maliit.github.io for more information about the project. Call for contributions Maliit’s website could benefit from a little love. Some of the information is no longer up to date. If anybody out there has some time to spare to fix it up a little bit, hop to github.com/maliit/maliit.github.io and send us a pull request. Should anybody with some influence at Canonical happen to read this announcement: We have nothing against the LGPL 3.0 but we’d like some consistency in our licensing. Maliit Keyboard was originally BSD-licensed but Canonical code from 2014 until 2017 is licensed under LGPL-3.0-only. If Canonical could send us a PR replacing the LGPL 3.0 headers with BSD ones, we’d appreciate it. We currently lack the manpower to crawl through various forks of Maliit Framework and Keyboard. We’re aware of them and we totally support the right of anybody to fork all Free Software code but not always is new code in those forks specific to custom implementations. A helping hand or two that ports improvements useful for our upstream code would, again, be very appreciated. [Less]

Maliit framework Fix usage of zwp_input_method_v1::content_purpose_digits Update input method area when activation is lost Load compose inputcontext plugin for physical keyboard handling Stop client crashing when ... [More] QGuiApplication::focusObject is null Clean up FindGIO.cmake to allow working with older cmake. Only allow focus removal from input items. Ensure orientation updates are always sent when valid Fix the broken tests build. Show the panel as the keyboard interface is reset Fix search for qtwaylandscanner on 32-bit architectures Do not build examples by default Add cmake option to build examples Maliit keyboard Remove label from language key on emoji keyboard Remove the unused and outdated styling support Support icon themes to load the icons Make sure Settings also work when running on Plasma left/right arrow keypress: Don’t check for surrounding text Bypass argument count problem for newPredictionSuggestions and newSpellingSuggestions Clean up unused code Let language features customize primary candidate index Recalculate primary candidates after refreshing candidate list Process pinyin sequence properly Handle partial candidate words in pinyin properly Allow force refreshing candidate list Allow delaying committing text when a candidate word is selected Provide appstream information Use Q_ENUM Optimise symbols for Simplified Chinese Use only valid pinyin symbols on pinyin keyboard Fix incorrect key name in tablet.json Don’t crash when no language plugin is loaded Where can I get it? framework: maliit-framework-2.1.0.tar.gz keyboard: maliit-keyboard-2.1.0.tar.gz What is it? Maliit provides a flexible and cross-platform input method framework. It has a plugin-based client-server architecture where applications act as clients and communicate with the Maliit server via input context plugins. Maliit is an open source framework (LGPL 2.1 or later) and an open source on-screen keyboard (LGPL 3.0 only). Maliit is being used by KDE for Plasma, LG for webOS, Ubuntu Touch, LuneOS, Sailfish OS, and likely others. Visit maliit.github.io for more information about the project. Call for contributions Maliit’s website could benefit from a little love. Some of the information is no longer up to date. If anybody out there has some time to spare to fix it up a little bit, hop to github.com/maliit/maliit.github.io and send us a pull request. Should anybody with some influence at Canonical happen to read this announcement: We have nothing against the LGPL 3.0 but we’d like some consistency in our licensing. Maliit Keyboard was originally BSD-licensed but Canonical code from 2014 until 2017 is licensed under LGPL-3.0-only. If Canonical could send us a PR replacing the LGPL 3.0 headers with BSD ones, we’d appreciate it. We currently lack the manpower to crawl through various forks of Maliit Framework and Keyboard. We’re aware of them and we totally support the right of anybody to fork all Free Software code but not always is new code in those forks specific to custom implementations. A helping hand or two that ports improvements useful for our upstream code would, again, be very appreciated. [Less]

After quite some while we are happy to release Maliit 2. Thanks for all the support to this release. Maliit Framework Not much has happened since our 0.99.2 release. Marius Gripsgard and Andrés B.S. fixed a few things around pkgconfig. At the ... [More] stable state Maliit is, we think it’s fair to assume that the next big changes will be the eventual port from Qt 5 to Qt 6 (not that we mind getting suprised with pull requests adding features before that). We will also look at supporting new Wayland Input Method protocols See the Wayland Protocols - Input Method Hub. Maliit Keyboard This release is a bit more exciting. Our last Keyboard release was 0.99.1 as part of the maliit-plugins bundle way back in 2015. Then Canonical came and forked the source code to build a virtual keyboard for Ubuntu Touch, made some improvements, and then went away again because they discontinued Ubuntu Touch. Nevertheless, their work was valuable enough to use it as base for further improvements and bringing the code back into the Maliit fold. From 2017 until somewhat recently, Jan Arne worked pretty much by himself on improvements such as removing deprecated Ubuntu Touch dependencies, porting the code from QMake to CMake, and so on. More recently the good folks at KDE looked for a new on-screen keyboard, though, and send in a few pull requests. With KDE and their Plasma project moving to Maliit, Linux distributions want proper releases of dependencies as well, so here it is. Where can I get it? framework: maliit-framework-2.0.0.tar.gz keyboard: maliit-keyboard-2.0.0.tar.gz What is it? Maliit provides a flexible and cross-platform input method framework. It has a plugin-based client-server architecture where applications act as clients and communicate with the Maliit server via input context plugins. Maliit is an open source framework (LGPL 2.1 or later) and an open source on-screen keyboard (LGPL 3.0 only). Maliit is being used by KDE for Plasma, LG for webOS, UBPorts, LuneOS, Sailfish OS, and likely others. Visit maliit.github.io for more information about the project. Call for contributions Maliit’s website could benefit from a little love. Some of the information is no longer up to date. If anybody out there has some time to spare to fix it up a little bit, hop to https://github.com/maliit/maliit.github.io and send us a pull request. Should anybody with some influence at Canonical happen to read this announcement: We have nothing against the LGPL 3.0 but we’d like some consistency in our licensing. Maliit Keyboard was originally BSD-licensed but Canonical code from 2014 until 2017 is licensed under LGPL-3.0-only. If Canonical could send us a PR replacing the LGPL 3.0 headers with BSD ones, we’d appreciate it. We currently lack the manpower to crawl through various forks of Maliit Framework and Keyboard. We’re aware of them and we totally support the right of anybody to fork all Free Software code but not always is new code in those forks specific to custom implementations. A helping hand or two that ports improvements useful for our upstream code would, again, be very appreciated. [Less]

There is a new standalone mode added to Maliit, which allows to just include the server into the plugin. Instead of having to run maliit-server and loading a keyboard implementation as a plugin one can just create a standalone executable (in ... [More] addition). That is already done for the new Maliit Keyboard 2 where a maliit-keyboard executable is created which can just be run with the Maliit DBus or the the Wayland input method protocol. In addition we updated the Wayland support in maliit-framework to use the zwp_input_method_v1 protocol used in weston currently. We also added a Qt wayland-shell-integration plugin for the input panel. With a maliit-keyboard.sh script like #!/bin/sh export QT_WAYLAND_SHELL_INTEGRATION=inputpanel-shell maliit-keyboard -platform wayland one can just use [input-method] path=/usr/bin/maliit-keyboard.sh to run maliit-keyboard inside weston again. [Less]

There is a new standalone mode added to Maliit, which allows to just include the server into the plugin. Instead of having to run maliit-server and loading a keyboard implementation as a plugin one can just create a standalone executable (in ... [More] addition). That is already done for the new Maliit Keyboard 2 where a maliit-keyboard executable is created which can just be run with the Maliit DBus or the the Wayland input method protocol. In addition we updated the Wayland support in maliit-framework to use the zwp_input_method_v1 protocol used in weston currently. We also added a Qt wayland-shell-integration plugin for the input panel. With a maliit-keyboard.sh script like #!/bin/sh export QT_WAYLAND_SHELL_INTEGRATION=inputpanel-shell maliit-keyboard -platform wayland one can just use [input-method] path=/usr/bin/maliit-keyboard.sh to run maliit-keyboard inside weston again. [Less]

There is a new standalone mode added to Maliit, which allows to just include the server into the plugin. Instead of having to run maliit-server and loading a keyboard implementation as a plugin one can just create a standalone executable (in ... [More] addition). That is already done for the new Maliit Keyboard 2 where a maliit-keyboard executable is created which can just be run with the Maliit DBus or the the Wayland input method protocol. In addition we updated the Wayland support in maliit-framework to use the zwp_input_method_v1 protocol used in weston currently. We also added a Qt wayland-shell-integration plugin for the input panel. With a maliit-keyboard.sh script like #!/bin/sh export QT_WAYLAND_SHELL_INTEGRATION=inputpanel-shell maliit-keyboard -platform wayland one can just use [input-method] path=/usr/bin/maliit-keyboard.sh to run maliit-keyboard inside weston again. [Less]

We forked the abandoned ubuntu-keyboard (which was originally based on maliit-plugins), removed the Ubuntu dependencies and pushed it into a new maliit-keyboard repository. It supports language layouts: Arabic, Azerbaijani, Bosnian, Catalan, Chinese ... [More] (Pinyin), Chinese (Chewing), Czech, Danish, German, Greek, English, Esperanto, Spanish, Persian, Finnish, French, Gaelic, Hebrew, Croatian, Hungarian, Icelandic, Italian, Japanese, Korean, Latvian, Norwegian, Dutch, Polish, Portuguese, Romanian, Russian, Slovenian, Serbian, Swedish, Ukrainian and an Emoji layout. The non-cjk languages support text prediction/correction via presage and hunspell. It is the new default keyboard for Maliit. [Less]

We forked the abandoned ubuntu-keyboard (which was originally based on maliit-plugins), removed the Ubuntu dependencies and pushed it into a new maliit-keyboard repository. It supports language layouts: Arabic, Azerbaijani, Bosnian, Catalan, Chinese ... [More] (Pinyin), Chinese (Chewing), Czech, Danish, German, Greek, English, Esperanto, Spanish, Persian, Finnish, French, Gaelic, Hebrew, Croatian, Hungarian, Icelandic, Italian, Japanese, Korean, Latvian, Norwegian, Dutch, Polish, Portuguese, Romanian, Russian, Slovenian, Serbian, Swedish, Ukrainian and an Emoji layout. The non-cjk languages support text prediction/correction via presage and hunspell. It is the new default keyboard for Maliit. [Less]