G’day everyone, long (long) time lurker, first time poster.
Over the last few months I’ve been working on a Terminal User Interface for ROS2. It’s written in C++, and uses Notcurses as the rendering library. I wanted to build something that was both fun to look at and use, which also made introspecting and interacting with a running ROS2 system less clunky.
A couple of gifs:
The current feature list:
- Echo/Plot topics
- Send receive service calls.
- View node list/information
- Probably a few others that I’ve forgotten.
I have plans in the future to implement the following:
- Interacting with actions/parameters.
- More topic visualisation methods, in the same vein as rosshow. Notcurses is very powerful, it doesn’t look like it’d be too difficult to implement video streaming or point cloud visualisation.
- Fuzzy search. For something like calling a service, my ideal workflow would look something like:
- Press ‘s’ for services
- Either use arrows to select, or just begin typing to show only fuzzy matched entries. So, typing something like ‘motor stop’ would show all services whose name contains both of those entries, in whatever order.
- Enter to select, enter again to display interaction form
- Simply fill out service, call, press enter to send it off, and view result.
I think this approach would greatly assist with situations where you’re stuck on a laptop in the field, and you’re trying to debug/test parts of a complex workflow.
- Adjustable theming. Currently, the colors are hard-coded, I intend on having it read from your terminal’s color scheme. It’s currently a bit hard on the eyes, to be honest.
- Proper mouse support. It’s not that I hate the mouse inclined, It’s just an afterthought currently. I’m pretty sure It doesn’t work in the latest release. Now that I’ve decided to make it public, I will be putting more time into it.
You can find the repo here: https://gitlab.com/juraph/ornis. If anyone has any interest in contributing, and would prefer to use github, don’t hesitate to let me know. I’m happy to re-host it there.
A word of warning, it’s more than a little buggy, and frankly a bit bad. I’m still working on that part. But, I know that I’ll never end up sharing it anywhere if I wait until I’m happy with it.
I also have a bit of a dev log of my work on ORNIS, although I’m using the term ‘dev’ and ‘log’ very loosely here.