Currently, touchpad X11 supports 3 different backends: evdev, synaptics, libinput. However touchpad Wayland only need libinput. Currently, they all mixed and this makes the KCM complex.
At the end of this patch, Touchpad KCM will be splitted into 2 different KCMs; kcm_touchpad (X11), kcm_touchpadw (Wayland)
This patch aims to followings;
1- The future is Wayland + Libinput so having a seperated KCM for it makes the development easier and gives the flexibility to the developer. This leads to more stability.
2- KCMs should2- touchpadw_kcm will be converted to KConfigModule and at. At the end of the patch, KDE'll have a simple Wayland + Libinput KCM in KConfigModule.
3- kcm_touchpad will be simpler too thanks to cleaning.
The need to this patch is occured when I'm trying to bring the touchpad libinput KCM support to X. Current complexity makes the development really confusing and that means bug. So after this patch, the work for touchpad libinput KCM support will be done.
The current patch strategy is as following:
Stage 1- Removing all wayland related things in the KCM. So that reviewers can see the difference easily.
Expected test result: In Wayland, there will not be a Touchpad KCM support since everything is removed about Wayland. In X11, there will be a fully-functional Touchpad KCM.
Stage 2- touchpadw_kcm will be created in plasma-desktop>kcms>touchpadw folder.
Expected test result: In Wayland, there will be shown a KConfigModule dummy Touchpad KCM, which will have a UI but not a functional backend. In X11, same as stage 1.
Stage 2- Wayland T3- kcm_touchpad KCM will be written in KConfigModule from scratch, whichw backend will be kcm_touchpadwfully written.
Expected test result: In X11 and Wayland, everything should be working fine.
Stage 4- kcm_touchpad will be cleaned and reorganized. This stage may be big. In this case, it will be created a new patch for it.
Future Patch- Libinput KCM support to X11!