[ros-users] ROS Clients that work out of the box without ROS .msg, .srv, and .action pre-compilation

[Santiago Bragagnolo]

Hi Aaron, in my implementation for Pharo smalltalk i do that, and for the
cases where i cannot use that, i have a node that install the types in a
parameter namespace in the master. For that case, you should have a master
in a ros installed environtment, but the type definition is centrally
accessible.



2015-01-06 6:22 GMT+01:00 Aaron Sims <aaron at happyartist.net>:

> Dear ROS-Users,
>
> I've been working on a ROS Client implementation in Java that does not
> require pre-compilation of .msg, and .srv (.action may or may not happen
> based on implementation requirements - I haven't researched enough to know
> if it has any special requirements).
>
> The .msg, and .srv can be compiled on the fly based on the message
> definition in most cases, and the implementers of ROS appear to of went to
> great lengths to ensure this potential functionality, by also including and
> nested Object type on the initial communication (Or maybe this is only done
> in turtlesim..., I assume not since turtlesim .msg definitions do not
> contain the additional Object types, this is a ROS specific technical
> implementation).
>
> Do the C++, and Python ROS Clients implement the functionality to convert
> incoming ROS Messages on the fly to native Objects? Or do they work in a
> similar manner to ROS Java requiring that a client manually compile the the
> .msg, and .srv files, then using those precompiled APIs, or are they smart
> enough to automatically write their own input and output data handler and
> auto generate their own Native Object for interpretation by the autonomous,
> semi-autonomous, or teleoperation controller?
>
> If this functionality is not implemented, the designers put in an awesome
> Easter Egg.
>
> Thanks,
>
> Aaron
>
> _______________________________________________
> ros-users mailing list
> ros-users at lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20150106/7d6b8f49/attachment.html>