Tag Archives: input method

The Road to Fcitx 5: 3. You can (NOT) type on wayland (properly).

Posted on November 6, 2017 by csslayer

With a few recent changes on Fcitx 5, Fcitx can now be used to type on Wayland. (Even the window is rendered with EGL! .. ok this is not important) And as of today, I’d say it is the first and … Continue reading →

Posted in fcitx development | Tagged , , , , , | Leave a comment

The Road to Fcitx 5: 2. With multiple focus and multiple display in mind.

Posted on October 28, 2017 by csslayer

I’d like to clarify one thing about this series of articles first. All features described in this series are already implemented, because I do not fell comfortable about writing about vaporware. The purpose of this series is to share some … Continue reading →

Posted in fcitx development | Tagged , , | Leave a comment

The Road to Fcitx 5: 1. libxcb replaces libX11

Posted on October 27, 2017 by csslayer

This is the first post of “Road to Fcitx 5”. I planned to talk about more the changes in Fcitx 5, and comments are welcome. Right now, I’m using Fcitx 5 from day to day. As you can see from … Continue reading →

Posted in fcitx development | Tagged , , , | Leave a comment

Gaps between Wayland and Fcitx (or all Input methods).

Posted on October 3, 2017 by csslayer

Though some people have no problem (or, only few problems) about using fcitx (to be more specifically version 4) with wayland, but the truth is there are still lots of problems left to be addressed. The truth is, wayland is … Continue reading →

Posted in fcitx development | Tagged , , , | 3 Comments

Fcitx 4.2.7

Posted on January 26, 2013 by csslayer

All components in this release will depend on fcitx 4.2.7 due to they are using the new build macro. Now we have a new template repo for whom want to develop new addon for fcitx: https://github.com/fcitx/fcitx-templates/tree/master And for kdevelop user: … Continue reading →

Posted in fcitx development | Tagged , | 9 Comments