You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to make a LifecycleNode in c++ and visited the GitHub page to learn about the interface and what I need in order to fulfil it. I had issues finding that information here, and I had more issues trying to learn from the links in the README. In lack for a clear tutorial, a good demo can suffice, I thought, and went looking, but could still not find anything helpful. I resorted to writing on ROS Answers, where I was linked to the Demo repo. This is what I was looking for.
Feature description
In order to make it easier for someone to use the code provided in this package, the README should link to the demos repository, since the demo repository contains demos of how to use this code.
Implementation considerations
It wouldn't be wrong to have an examples folder in this repo either, I think, but an easy solution to make LifecycleNodes (in particular) more approachable would be to link to somewhere they are used.
The text was updated successfully, but these errors were encountered:
Feature request
Background
I wanted to make a LifecycleNode in c++ and visited the GitHub page to learn about the interface and what I need in order to fulfil it. I had issues finding that information here, and I had more issues trying to learn from the links in the README. In lack for a clear tutorial, a good demo can suffice, I thought, and went looking, but could still not find anything helpful. I resorted to writing on ROS Answers, where I was linked to the Demo repo. This is what I was looking for.
Feature description
In order to make it easier for someone to use the code provided in this package, the README should link to the demos repository, since the demo repository contains demos of how to use this code.
Implementation considerations
It wouldn't be wrong to have an
examples
folder in this repo either, I think, but an easy solution to make LifecycleNodes (in particular) more approachable would be to link to somewhere they are used.The text was updated successfully, but these errors were encountered: