Based on http://www.cplusplus.com/doc/tutorial/files/, it appears that file I/O would be VERY easy to implement into Gopher.
Here's what I think could work for Gopher:
- Upon launch: Gopher will check for, and if not created, create "gopher.ini". If it creates it, it will autofill with the initial file's contents/bindings.
- If Gopher FINDS gopher.ini, it will read absolute-ordered bindings (ignoring the first 3 lines, which will contain "comments").
- The comments will list the order of controller devices that the lines are read to.
Example file, with line numbers added:
1;This is Gopher's bindings, it is created by Gopher automatically upon first run.
2;Bindings are read in order: A, X, Y, B, RBumper, LBumper, LAnalogClick, RAnalogClick, DPUp, DPDown, DPLeft, DPRight, Start
3;Valid "operations" to add to the lines are as follows: up, down, right, left, start, enter, lclick, rclick, middleclick, changespeed, NONE.
4;lclick
5;rclick
6;NONE
7;enter
8;NONE
9;changespeed
10;middleclick
11;up
12;down
13;left
14;right
15;start