yes, I was talking about the statement below
The idea is to use buttons from the "Remote" or "Gamepad" folders to get the same functionality that is on the XBMC on the XBOX when using a remote or a gamepad, as "Remote" and "Gamepad" buttons are defined in XBMCs "Keymap.xml" and thus are context sensitive and then to complement any missing functions from the different action groups that are not context sensitive.
... I'm a bit confused as to the way you intended it to be used. I could be using it wrong. Though I don't think there needs to be a huge how-to.
I feel the readme needs to accomplish your intended usage method...
a) what sections/folders should be populated first
b) what sections/folders are populated, as needed and how these affects functionlaity
Something like this (again, this may be incorrect as I may not understand your design fully)...
'Remote' is the main folder to use - Put all your general commands here first. Example: navigating menus, starting/stopping playback, etc.
Other folders are used based on their context in XBMC. If there are buttons/commands you wish to remap based on specific context in order to control differently that the commands in the 'Remote' folder.
Example:
'Remote' folder "Arrow Up" moves the menu selection up one item. You can map "Arrow Up" inside 'Media Playing' folder to mean something different.
setup... XBMC, W7MC for DVR & Live OTA TV, JRMC for multi-zone audio, EG, MiCasaVerde Vera3, USB-UIRT IR receiver, Harmony remote, 5.2 home theater system