Re: [Ros-sig-gui] FW: Fuerte SIG: ROS GUI

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Dirk Thomas
Date:  
To: ros-sig-gui@code.ros.org
Subject: Re: [Ros-sig-gui] FW: Fuerte SIG: ROS GUI
Hi Dave,

> I will chime in from Willow Garage that we are looking to move to Qt generally, so help in porting the rx* tools to Qt is very welcome. I am working on moving rviz to Qt even now, and I hope that it
> (or some part of it) will be able to plug into the rosgui framework as well.


Hopefully we can win the maintainers of the individual tools over to work on the porting...

> Dirk: can rosgui plugins run standalone as well, or do they only function inside the framework? It occurs to me that it might be nice if they could go either way. Maybe it's as simple as making a
> wrapper script that brings up a rosgui frame with exactly one plugin in it?


No and Yes ;-)

A plugin can not run fully standalone as the functionality provided by the framework (i.e. creating the QApplication, QMainWindow etc.) is missing.
A wrapper script would need to mimic the same behavior as ROS GUI and interact exactly as ROS GUI does (which would require quite some code).

But therefore the ROS GUI has a command line option "--standalone <PLUGIN-NAME>" which can be used to start the framework with only this specific plugin.
Other stuff like menu bars, perspectives etc. are then disabled.
The plugin can still save it's settings and they are restored if you start the ROSGUI again with the same standalone option.
I hope that is the feature you think is needed.

I have just pushed another commit to GIT which adds additional CLI options:
   -h, --help            show this help message and exit
   -b BINDING, --qt-binding=BINDING
                         choose Qt bindings to be used [pyqt|pyside]
   -l, --lock-perspective
                         lock the GUI to the used perspective (hide menu bar
                         and dock widget close buttons)
   -p PERSPECTIVE, --perspective=PERSPECTIVE
                         start with this perspective
   -s PLUGIN, --stand-alone=PLUGIN
                         start only this plugin (implies -L)
   --list-perspectives   list available perspectives and exit
   --list-plugins        list available plugins and exit


Especially "--list-plugins" is useful so that you do not have to guess the plugin names.
But you could also provide only a part of the plugin name (as long as it is unique in the list of all plugins).
Some kind of auto-completion for those arguments would be nice but would require to put a file to the ROS folder...

Dirk
_______________________________________________
Ros-sig-gui mailing list

https://code.ros.org/mailman/listinfo/ros-sig-gui