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?)
Yes that will work.
I think the UI will be different than currentIy or the mockup because I learned this weekend actions can have more than two active shortcuts which should IMO all be possible to be changed/removed.
Update after a long time:
I found time to work on this again. The basic functionality is there, i.e. displaying/changing of shortcuts. Nicely seperated in a model and qml frontend. What's missing is the schemes import/export. Also the ui could use some input :D. I will probably upload a wip diff this weekend or next week.