2014-12-14, 23:26
Glad you guys like it. Is the general concept OK? Can the underlying assumptions be improved?
Currently we have one mapping for each system, and one "default" for Kodi itself. The default has Kodi functions like "select", "scroll", etc. The console will have controller buttons. For *most* controllers, the NES screen will look exactly like:
Is this what we want?
Getting this right is critical, because it directly dictates the demands of the Peripherals API and the Game API.
I mentioned this above,
These decisions are exactly the kind that should be set by the community, instead of a single developer or user who "knows best". We can make keymaps "data-driven" by collecting keymap data and defaulting to the most popular configurations.
Currently we have one mapping for each system, and one "default" for Kodi itself. The default has Kodi functions like "select", "scroll", etc. The console will have controller buttons. For *most* controllers, the NES screen will look exactly like:
Code:
Select: Select Start: Start
.D-pad: D-pad B: B
A: A
Is this what we want?
Getting this right is critical, because it directly dictates the demands of the Peripherals API and the Game API.
(2014-12-14, 20:38)OmniBlade Wrote: Looks like the standard layout table is a little off. Assuming we are basing the layout on the xbox360 layout being correct, the 1 should be cross on the PS layouts and B on the Wii layouts, 2 should be circle on the PS and A on the wii, 3 should be Y on Wii and 4 should be X on the Wii.
I mentioned this above,
Quote: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.
These decisions are exactly the kind that should be set by the community, instead of a single developer or user who "knows best". We can make keymaps "data-driven" by collecting keymap data and defaulting to the most popular configurations.