Abstracting key events from operable actions in components

[lukewilson2002]

Currently, every component handles key events their own way. This makes it impossible to change key bindings without recompiling the editor. Imagine if you could change your keybindings for any component or action without even restarting the editor. I know so futuristic.

So I want to make input events be triggered and handled at a core input loop level. The events are matched against a database which is the keybindings, and then based upon what a key matches against, we issue it to the component if it is focused. If the component is not focused and it was found to be the handler for our key, we just go to the next available component. Again, kinda based on the first-come first-serve rule I like to follow with this editor.