Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add cpp version for urdf_tutorial #4926

Open
wants to merge 10 commits into
base: rolling
Choose a base branch
from

Conversation

Demonmasterlqx
Copy link
Contributor

No description provided.

some command to launch debug demo is wrong and correct it

Signed-off-by: Demonmasterlqx <[email protected]>
…obot-State-Publisher-py.rst

change name

Signed-off-by: Demonmasterlqx <[email protected]>
add cpp version

Signed-off-by: Demonmasterlqx <[email protected]>
add 
.. redirect-from::

    Tutorials/URDF/Using-URDF-with-Robot-State-Publisher

Signed-off-by: Demonmasterlqx <[email protected]>
Copy link
Collaborator

@kscottz kscottz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Demonmasterlqx, thank you so much for your contribution! We really appreciate it.

I sent over a bunch of suggestions. Before I approve this I would like to see more comments in main C++ source file. It really helps users when we document the example code in excruciating detail.

Other than that I think we have to discuss the copyright of the code cited in pull request. I don't think it is a problem, but we need some clarity on how to handle it appropriately.


Fire up your favorite editor and paste the following code into ``urdf_tutorial_cpp/src/urdf_tutorial.cpp``

.. code-block:: cpp
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section is good but I would really like to see the code commented in excruciating detail. Telling the user what to do is good, but telling them why they should do it is better.

A good rule of thumb is that every time there is a whitespace break you should include a comment.

-------

You created a ``JointState`` publisher node and coupled it with ``robot_state_publisher`` to simulate a walking robot.
The code used in these examples is originally from `here <https://github.com/benbongalon/ros2-migration/tree/master/urdf_tutorial>`__.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fujitatomoya how should we handle the copyright on this kind of stuff?

The code used in these examples is originally from `here <https://github.com/benbongalon/ros2-migration/tree/master/urdf_tutorial>`__.

Credit is given to the authors of this
`ROS 1 tutorial <http://wiki.ros.org/urdf/Tutorials/Using%20urdf%20with%20robot_state_publisher>`__
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we need these lines.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I just copy these form python version. So I tend to delete them. QWQ

@Demonmasterlqx
Copy link
Contributor Author

Hi @kscottz ! Thank you so much for helping me to polish my words and give some suggestion. I have add some code comment into code blocks and polish my words

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants