The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It seems that you would be better served if you first develop an API that is subsequently used with a light ROS wrapper to manage messaging and other housekeeping.
I do not know your code but when I hear "link different minds to different robots", it sounds like you would have to define and effective abstraction for the mind software that you are developing. This has nothing to do with ROS, and if you wanted to share your code, you would face the same issue if developing this application for Unity, Second Life, or any other tool/environment.
The language, and the framework you use to structure your project also will impact how easy it will be to use in other languages/distros/etc.
Things to consider as well: Do you plan to develop something that plays nicely with SWIG? Can you develop a C library that could be imported with ctypes (python), or LoadLibrary (Java)? What are the languages that are required by the tools you'd like to develop for? Do you know the places that useful methods like sleep() or say() are defined?
At the end of the day, it comes does to what are you willing to do, and how much you (plan to) understand about the potential users of your API.
Just my 2 cents. I really hope it helps.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
