2014-12-14, 08:55
I'm designing the GUI controller configuration utility. Any feedback is appreciated.
Here, the user configures A, selects the label from a list, then configures B, and selects the label from a list. Pay close attention to how the list options, and their order, is inferred from my controller analysis above.
http://pastebin.com/5ham9T0R
Here, the user configures A and B but in the opposite order. Pay close attention to how the list options differ from above. Again, notice how the selection and order of the suggested labels are derived from the data.
http://pastebin.com/KXbMtwbZ
Here, the user performs the first example but with a PS1 controller, and then goes on to configure the next two buttons. Notice for button 3, likely labels for button 3 and 4 are both offered. This reflects my assumption that users will have a different idea of whether square comes before triangle, or triangle comes before square. (this is also why both A and B are presented for the "OK" button). Eventually, if we collect keymaps on a massive scale, it will be possible to mine the data for these subjective differences.
http://pastebin.com/FPH6eGpe
Here, the user only has four main buttons, so decides to use the combination A+B for button 5 and X+Y for button 6... but doesn't perform the configuration in the order you'd expect. It's OK though, because the label for button 6 can cope with this.
http://pastebin.com/9ApgJapk
So, is this data-driven approach worthwhile, or is it way too over-engineered?
Here, the user configures A, selects the label from a list, then configures B, and selects the label from a list. Pay close attention to how the list options, and their order, is inferred from my controller analysis above.
http://pastebin.com/5ham9T0R
Here, the user configures A and B but in the opposite order. Pay close attention to how the list options differ from above. Again, notice how the selection and order of the suggested labels are derived from the data.
http://pastebin.com/KXbMtwbZ
Here, the user performs the first example but with a PS1 controller, and then goes on to configure the next two buttons. Notice for button 3, likely labels for button 3 and 4 are both offered. This reflects my assumption that users will have a different idea of whether square comes before triangle, or triangle comes before square. (this is also why both A and B are presented for the "OK" button). Eventually, if we collect keymaps on a massive scale, it will be possible to mine the data for these subjective differences.
http://pastebin.com/FPH6eGpe
Here, the user only has four main buttons, so decides to use the combination A+B for button 5 and X+Y for button 6... but doesn't perform the configuration in the order you'd expect. It's OK though, because the label for button 6 can cope with this.
http://pastebin.com/9ApgJapk
So, is this data-driven approach worthwhile, or is it way too over-engineered?