Allright. I took a look into the details, API etc.
First of all AirConsole looks very promising. It's really cool! Even though local multiplayer is not so popular as it was years ago, this technology seems to be able to turn the time back in some manner ... and it gives us (C2 developers) one more platform where we can build very interesting games (cause this platform needs a specific approach) and monetize them.
Regardging working with C2. For now there is an option to build only the screen part with C2, and the controller part has to be made manually (coded). I know there is a controller generator, but that is very limited if you don't know much about coding (and most of C2 people don't).
It would be absolutely outstanding if you guys could make some official agreement... what I mean here:
1. AirConsole Team: extend the C2 plugin to be able to send data from controller to the screen. That's basically just a send message, so your part is easy
2. Scirra add an official export to AirConsole. This would be basically an HTML5 export but would have to cover an option while exporting to pick the screen export or controller export (the difference between those two is actually trivial). In this situation we would be able to build a C2 app for the screen and a C2 app for the controller separately which will give us a possibility to build nice fancy controllers with animations etc.
So the AirConsole export would have to separate C2 data files into subdirectories basically so the output would be something like:
For AirConsole export (with screen option selected)
gameDirectory/
screen.html //this is just a renamed "index.html" with changed references to the libraries etc. to "screenDataDirectory/*" instead of "./*"
screenDataDirectory/ //here would be all the C2 data files except the index.html
[/code:pipaxeqy]
[b]For AirConsole export (with controller option selected)[/b]
[code:pipaxeqy]gameDirectory/
controller.html
controllerDataDirectory/[/code:pipaxeqy]
[b]And the final output would be[/b]
[code:pipaxeqy]gameDirectory/
screen.html
screenDataDirectory/
controller.html
controllerDataDirectory/[/code:pipaxeqy]
As I believe the renaming index.html to controller.html (or screen.html) is trivial to do, I don't know how much work to do is to change all the files/libraries dependencies so the main html file would search for the data in the subdirectory.
I took a quick look into c2runtime.js and I see there is no "path" variable, everything is being fetched relatively from the "./" folder, so it won't be just a matter of changing the variable. Anyway didn't go into details of this (huge ) file.
@Ashley could you tell if this is something that could be done with relatively no effort or it's pretty much of work? Or maybe you can give some hint's how to do this manually? I mean if there are just several places to change like:
[code:pipaxeqy]var datajs_filename = "data.js";[/code:pipaxeqy]
to
[code:pipaxeqy]var datajs_filename = subDir + "data.js";[/code:pipaxeqy]