Hi Vincent,
A group of us are working on similar ideas over at Robot Web Tools http://robotwebtools.org/
The community has a large number of tools to expose, work with, and visualize ros topics, services, and action services to the web. Our previous efforts have focused on getting a framework that allows many types of interfaces to be built. These tools could be used to create a web-based rviz or rqt etc.
If you’re interested in such things please feel free to join the community effort!
Best regards,
Sarah Osentoski
Robert Bosch LLC
Research and Technology Center (CR/RTC-NA)
4005 Miranda Avenue, Suite 200
Palo Alto, CA 94304
www.BoschResearch.comTel:1 (650) 320-2969
Fax: 1 (650) 320-2999
Sarah.Osentoski@us.bosch.com
From: ros-users-bounces@lists.ros.org [mailto:ros-users-bounces@lists.ros.org] On Behalf Of Vincent Rabaud
Sent: Wednesday, June 25, 2014 1:05 PM
To: User discussions
Subject: [ros-users] Web introspection tools
At ROS Kong, some rQt on the web was demoed as well as a Gazebo web visualizer.
I am no expert in web programing but what prevents us from moving rQt and RViz to the web/javascript ? The obvious advantages would be cross-platform support, optimizations independent of the underlying libraries, easier code to debug, no compilation. Plus, there are already great tools like robotwebtools and rosbridge.
Here are a few reasons I was told that could prevent that move; are those really valid ? Are there better reasons ?- hard to access local files (html is not aware of local files)
- no customizable shaders in WebGL (is that the case ? do we need those ?)
- slow JSON parsing libraries (aren't those optimized in recent browsers ?)
- heavy bandwidth usage (how about binary JSON ?)
_______________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users