The configuration tab has been completed! This allows a user to hook up a pad and map the gamepads buttons to the browser's reporting of its inputs.... gamepad.js stores these configurations for common browser/os/gamepad combinations... but this tab basically allows for quick integration of new or unkown gamepads and an obscure browser/os/gamepad combinations!! So sick!
I will probably adjust the text to have one area that says (XBOX 360) with no player num... and then switch that text to the button they need to press. Player number is irrelevant since we are mapping gamepad "type" only... so it scans all gamepads with this specific type regardless of player num... also super sick... unless you have a jerk friend who likes to press keys on another gamepad with the same "type" while you are trying to configure your gamepads... not our problem... I suggest denying your friend a beer for this act...
Next is finishing the action mapping tab... this is mapping game actions to inputs (gamepad / keyboard / mouse)... very exciting!