In the gesture customization mini-sprint with @nclarius earlier this year, we documented some requirements for mapping gestures to actions. There are different types of gestures in addition to keyboard shortcuts, extra mouse button bindings, game controller combos etc., so we named the requirements document ["Triggers and Actions"](https://community.kde.org/Goals/Input/Triggers_and_Actions). This issue is for discussing what the config file format for gesture/action mapping should look like. I'm thinking it doesn't have to be restricted to gestures only, instead we can have a single format that's usable for a wide variety of automation use cases. I'll leave the issue description open-ended like this, and post our two alternative config approaches as comments below. We can refine and discuss from there. Before questioning the need or scope of a given config option, please make sure to read the requirements document linked above and consider how a proposed change would affect the other documented triggers and actions listed in there.