Closed TheJJ closed 8 years ago
I'll start working on this.
I guess after #284, only the "read-keybindings-from-file-or-whatever" part remains to be implemented.
I would like to begin contributing to this project, and I think this is a good way to start. I'll work on reading these key bindings from a configuration file.
You might want to cooperate with @Elnabo then as I believe he already has started doing it in the meantime. (#526, #486)
I didn't work on the reading part. But here is what I know about it, and what may be needed.
The keybinds are now part of the generic config file(s). The config file reading should be done in python to be easily integrated with the cvar system (#486).
So I think you should focus on extracting any kind of couple key/value and if possible have a possibility to save modification.
I think that #537 has completed this issue, isn't it ?
YES! YES IT HAS!!!!
:beers:
Maybe store it as key-value pairs in
~/.openage/keybindings
.This file should have a config version on top once the format gets more sophisticated to perform/detect updates.
Ideally, the bindings are managed in it's own subsystem (
libopenage/cvar
?) to allow central storage and changes. The keys should probably point to functions that can be replaced at runtime. Avoid string lookups please.depends on the cvar config subsystem from #486