From @danielrr7
Side note / small suggestion:
It could be nice to have some kind of configuration file for the ncurses dashboard, so it can start already tracking the desired topics.
It might also be useful to support namespaces, so the same config file can be reused across different robots or instances.
For example, in another node I’m using a similar setup via a ROS2 YAML file:
Where:
If the topic starts with /, it ignores the node namespace.
If it doesn’t, it takes the node namespace (same as ROS2 subscriptions by default).
Just an idea that might make it even more flexible 🙂
This is just a brainstorming. Anyways, it’s really cool to see tools like this being developed.
From @danielrr7
Side note / small suggestion:
It could be nice to have some kind of configuration file for the ncurses dashboard, so it can start already tracking the desired topics.
It might also be useful to support namespaces, so the same config file can be reused across different robots or instances.
For example, in another node I’m using a similar setup via a ROS2 YAML file:
Where:
If the topic starts with /, it ignores the node namespace.
If it doesn’t, it takes the node namespace (same as ROS2 subscriptions by default).
Just an idea that might make it even more flexible 🙂
This is just a brainstorming. Anyways, it’s really cool to see tools like this being developed.