functional prototype: options/config menu

[jackmakesthings]

Don't currently know what these fields will be, so this ticket is limited in scope:

• [x] Is reachable via a button on the splash screen (see #74)
• [x] Includes a "back" button that returns to the splash screen
• [x] Shows a label ("config" or "options" or "settings" or whatever)
• [x] Includes an assortment of fields, which can be changed and saved - preferably to a file. (File can be hardcoded for now.)

Specific types of fields to try including:

• [x] Simple text/string edit (via LineEdit; optional more complex input via RichText or similar)
• [x] Boolean toggle
• [x] Numerical value (Spinbox? Range?)
• [ ] File/file path
• [x] Color picker (hey, who knows, maybe for use in a 'colorblind mode'?)

Once data is successfully saving to a file:

• [x] On entering this view, fields are populated either from file or defaults (or defaults in file, might be the most straightforward way to set this up)

Future tickets will refine things like file saving/choosing/overwrite behavior, dynamic paths, multiple options files, etc.

[jackmakesthings]

@Batbro could use your input on this one. Can you give me a general list of options you think a game like ours should provide via the config menu? Incomplete/rough is fine, this will be a starting point we can refine and add to.

For options that would have a default (including anything that's on/off), include what you'd want the default value to be.

My thoughts so far:

• UI settings:
  alternate color options
  maybe font-size?
  maybe even allow UI layout customization; i want to do some research about this
  thought: what if we allowed minor customization for the Trace sprite, like setting the accent color? could help with accessibility. if we wanted to really push it, we could even have different body models for the player to pick from. (Non-gendered, but different heights, proportions, mechanical detailing, etc.) This would mean drawing a lot more sprites, but might be cool enough to be worth it.
• Input mapping - this is complex enough to merit its own issue, but basically, allow users to rebind keys. Would really like to build a "navigate via keyboard" mode as well, for non-mouse users (note to self: open issue for that too)
• Autosave (on/off, defaults to on- if on, do we allow the player to set frequency?)
• Handicap/difficulty - We haven't discussed this much, but maybe we should

What else?