GSoC/2018/StatusReports/GunPark: Difference between revisions
No edit summary |
|||
| Line 7: | Line 7: | ||
==Current progress== | ==Current progress== | ||
* UI | * UI | ||
** Ported 90% of the existing UI to Qt Quick | ** Ported 90% of the existing UI and functionality to Qt Quick | ||
** Make model more flexible for incorporating IMs by using proxy models | ** Make model more flexible for incorporating IMs by using proxy models | ||
** Basic support for configuring fcitx | ** Basic support for configuring fcitx | ||
Revision as of 04:06, 7 June 2018
Port Keyboard input modules and Expand scope to cover input method configuration
Project Goals
Port all the Keyboard KCM's existing functionality to the new modern Kirigami UI, and make it easier for users to configure the IM from within System Settings.
Current progress
- UI
- Ported 90% of the existing UI and functionality to Qt Quick
- Make model more flexible for incorporating IMs by using proxy models
- Basic support for configuring fcitx
- Daemon
- Removed most of the legacy and cruft, such as tray icons and flags
The new architecture
| Xkb is enabled | Fcitx is enabled | Wayland is enabled | |
| Layout switch (rotate) key press | Apply miscellaneous config changes (originally global configs from the "Advanced" tab), and then switch the layout as usual using setxkbmap | set fcitx' "special" first layout to the one configured in the kcm, and then switch to the specific IM using dbus | let Kwin handle it (might have to change the kwin code too, since the config contains non-xkb layouts too) |
Blogposts and Links
Clone repository: https://cgit.kde.org/clones/plasma-desktop/gpark/gsoc-kcm-keyboard-revamp.git/?h=new_keyboard_kcm
My first blogpost: https://medium.com/@mujjingun_23509/google-summer-of-code-porting-keyboard-kcm-to-qt-quick-862d16e58d3c
Somebody mentioned that the xkb options in the "Advanced" section should not go away, I'm planning to put them under each layout's specific options.