Hi Benoit,
Thanks for sending this pointer along. websocket_gui looks pretty useful. I was able to run your demo, which is pretty nice:
http://dl.dropbox.com/u/14050575/tmp/Screenshot-Turtle%20Example%20-%20Google%20Chrome.png
However, it took a little more than following the Electric instructions. I had to clone flot separately and copy OpenLayers.js from its repository to a place where the Makefile would be happy. There maybe a more elegant way to do this as I am not the most experienced github user.
---
rosjs is another larger issue. There are many different "ros.js"es that are popping up. The ros.js from brown-ros-pkg still tends to be the default for rosbridge v1. For v2, the rosbridge_suite stack has a several ros.js files for directly using rosbridge v2 or emulating the behavior of v1. Further, Brandon Alexander has an AMD-compatible [*] rosjs (
https://github.com/RobotWebTools/rosjs) under the RobotWebTools organization. This will get out of control quickly.
To help bring a little more structure, we will be moving to RobotWebTools as the main portal for the various versions of rosbridge, rosjs, and related packages. This portal will most likely emulate the wiki structure of
ros.org such that related projects can easily index into the larger body of applications tools. More details will be coming soon.
That said, rosbridge will remain a general robotics protocol and not just a web interface for ROS.
-Chad
[*] Asynchronous Module Definition (AMD)
You received this message because you are subscribed to the Google Groups "Rosbridge Users" group.