See T8434 for some ideas regarding better usability, which is currently problematic in both the current design as well as the mockup above.
In particular, I'm referring to the tree view idea, i.e. dropping the separate list on the side. Interestingly, that would be similar to KDE3's KControl shortcuts module.
I started rewriting the KCM because I was annoyed at the inconsistency of the list representation (even though I fixed that in the meantime). I am going for the backend model in C++ with a Qml frontend approach.
- Displaying the components, actions and shortcuts
- Global filtering: Hiding of components that don't match the entered query and don't have actions or shortcuts that do either
- Setting shortcuts
- the whole scheme thing
- Performance: My hacked together qml seems to do be a bit slow sometimes (but maybe only because of debugging or having gammaray attached?)