Christian,

Since you are making the assumption that you have a Linux PC running on the robot and network access to that robot, would it make sense to use a web interface (like the still in development http://www.ros.org/wiki/web_interface) for visualization and control?

For example, there is http://www.ros.org/wiki/navigation_application that (and I'm only guessing based on name and some of the source files) looks to be the start of a web-based version of nav_view (or something close). Seems to me that gets around the cross-platform problems as, with the server running on Linux, there is no special cross-compiling; it also helps with the commercial app user base because all your customers need is a supported web browser (hopefully a recent version of Firefox or Chrome would suffice), which may be easier to support than Windows XP up to Windows 7, Mac OS X and Linux in all its flavors.

Not saying that ROS support for Windows wouldn't be a good thing, just that, in this case, perhaps a web interface would be better/easier than getting all of ros, navigation and visualization to run on Windows natively.

- Eric

On Mon, Aug 23, 2010 at 4:13 PM, Josh Faust <jfaust@willowgarage.com> wrote:

APIs needed are roscpp, common_msgs, tf and actionlib.

The generation of messages could be done on the Linux system and then
copy the cpp files to the Windows source tree, right?


Yes
 
Would you expand your statement about creating vcprojs for roscpp to the
other APIs?

You could probably do so, but the more packages you add the larger the task becomes.  At some point it starts to make more sense to actually support windows through the whole toolchain -- I don't know when that tipping point happens though.

Josh

_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users