-
Notifications
You must be signed in to change notification settings - Fork 28
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
Porting to ROS2 #22
Porting to ROS2 #22
Conversation
b9e233c
to
3574d8c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 after reviewing feedback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As with previous PRs please separate different unrelated changes into separate commits (or even better PRs).
9450e68
to
34a2fdc
Compare
@dirk-thomas @mlautman The rosgraph.impl.Graph file has been merged in a separate PR and this PR was rebased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again: if the style changes would have been separated from the actual changes it would be easy to apply them on the ROS 1 branch and significantly reduce the divergence between the branches.
setup.py
Outdated
('share/' + package_name + '/resource', ['resource/RosGraph.ui']), | ||
('share/' + package_name, ['package.xml']), | ||
('share/' + package_name, ['plugin.xml']), | ||
('lib/' + package_name, ['scripts/rqt_graph']) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it need both - an entry point and the global script?
@dirk-thomas Changes made per your comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes made per your comments
Since you rewrote history with a force push I can't see the changes you have made since the last review. That means I have to re-review the complete patch again. Please don't do that when incrementally reviewing patches. Either use the "squash and merge" option at the end or rewrite the history before merging but after the review has been finished.
Oh shoot, sorry Dirk |
Does this work with Crystal or is it using any API introduced after the release? In case of the former should this package be released? |
It uses the rclpy functions introduced in this PR (ros2/rclpy#247):
|
👍 That PR is part of the Crystal release. I will go ahead and run |
This ports rqt_graph to ROS2. Because rosgraph does not exist in ROS2, I grabbed and modified the rosgraph.impl.Graph code. Most new logic for ROS2 was put in the
_graph_refresh
method.