Here are some basic instructions for working with the Android version of Control if anyone wants to help port it.
In the file that is currently called "Sample.java" (this needs to be renamed to Control.java) there is a single line that points to the index.html file that gets loaded. It reads like so:
super.loadUrl("file:///android_asset/www/index.html");
If we take the entire www folder used by Android and then copy it to your local webserver you can then change the above line of code to something like the following:
super.loadUrl("http://192.168.1.7/~charlie/www/index.html");
... where you substitute your IP (localhost won't work, even in the simulator) and the path to your webserver.
The advantage of doing this is that we can then refresh the WebKit view at which point the -entire- javascript / html / css will be reloaded. So you don't have to continuously load new projects into the emulator while debugging javascript. Just hit the big "REFRESH" button that is currently on the screen (it needs to be moved someplace more manageable).
All the refresh button does is call: window.location.reload(); standard javascript for refreshing the page.
As it stands now, interfaces can be downloaded from webservers using the + button on the Interfaces page. The widgets should respond correctly to touch events, however, no OSC or MIDI is being generated yet. Also, the first time you download an interface the dimensions will be screwed up... if you quit Control and launch it again the interface (which will now appear in the interfaces menu upon launch) should look better.
Let me know if there are questions!