Open rbonghi opened 9 years ago
"or_interface" maybe too generic... "Interface to what?" should be the main common question that can come in my mind...
"or_brd_interface" can be used to specify that this is a interface to a board.
but the "ROS" information is still missing
"or_ros_brd_interface" o "or_ros_brd_iface" should be more complete, but I do not like it as much.
A simple "or_ros_motor_drv" should be good... what do you think?
"ORCoInterface" and the other lib can renamed as "ORCoJ", "ORCoC", "ORCoC++","ORCoROS", ...
See the capitalize, is important
In the ROS convention you should not use capital letters for package name
With new branch #20 I've reorganized the folders and files in two different nodes.
I propose a new name for this repository:
+1
2015-05-07 10:42 GMT+02:00 Raffaello Bonghi notifications@github.com:
With new branch #20 https://github.com/officinerobotiche/ros_serial_bridge/pull/20 I've reorganized the folders and files in two different nodes.
- orbus_msgs -> all messages
- ros_serial_bridge (new proposed name: _orbusinterface ) -> hardware interface to connect with the boards.
I propose a new name for this repository: ros_orbus_interface
— Reply to this email directly or view it on GitHub https://github.com/officinerobotiche/ros_serial_bridge/issues/6#issuecomment-99774945 .
Walter "Myzhar" Lucetti
email myzhar@robot-home.it web: www.robot-home.it http://www.robot-home.it/ - www.opencv.it http://www.opencv.it/ project: http://myzharbot.robot-home.it
Renamed in ros_orbus_interface
In according with the ROS convention http://wiki.ros.org/ROS/Patterns/Conventions
I want to rename this package in: orbus_interface
and the node in: unav ( alternative rosunav_node)
The runtime node will be this pattern:
rosrun orbus_interface unav
I would like to change name to this board in: or_interface, what do you think?
@Myzhar @katodo @bobboteck