> So I should add the few controller reserved functions to the plugin as well I guess?
I would say that we don't need/want the ability to add html elements, but I would need to take a look at the rest of the controller API to see what else is missing. I can't remember what was there off the top of my head, as I haven't look at the API since last fall. Things like getNickname and getDeviceId would be good though.
Ahh. Back at the computer now. I'm having a look through the AirConsole API, and I see the following things that a controller might use. I tried to go through your code to determine what remains to be implemented, and I apologize if you included something already that is in this list:
(static, constant) ORIENTATION_LANDSCAPE :string
The landscape orientation.
airconsole-api/airconsole-1.7.0.js, line 78
(static, constant) ORIENTATION_PORTRAIT :string
The portrait orientation.
airconsole-api/airconsole-1.7.0.js, line 72
(static, constant) SCREEN :number
The device ID of the game screen.
airconsole-api/airconsole-1.7.0.js, line 66
onDeviceMotion(data) *** - This one wasn't in X3M's version, but is necessary for accelerometer controls
storeHighScore(level_name, level_version, score, uid, data, score_string)