Hi all -
I think the time has come to get the process started of figuring out
what is going to happen to roslaunch. The SIG wiki page (http://
www.ros.org/wiki/sig/roslaunch) has 11 proposals, which I'll summarize
here:
* <launch> tag: adding 'name' and 'description' attributes
* Dependencies: "launch prog X once Y is running"
* Adding 'machine' attribute to <include> and <group> tags
* Bubbling up/passing through args
* Parameters: this is possibly a separate topic, but parameters and
the parameter server are a part of the launch process that account for
a lot of wasted developer time in practice.
* 'description' or 'doc' attributes for <arg> tags
* Automatic CLI documentation for launchfile arguments and tab-
completion.
* Add topic remapping to <include> tags.
* Add respawn attribute to <include> tags to relaunch the include if
any nodes it launched die.
* Add something similar to inclusion guards like a <once> tag to
prevent a given block of launchfile markup from being evaluated
multiple times.
* Allow binaries that are not in ros packages to be roslaunched
If anyone has any additions, please try to add them to the wiki in the
next few days. Once we have a full list, there are a few things to be
done: prune out any that would be better handled outside of roslaunch;
order proposals by desirability; determine feasibility of each
proposal; pick a final list to implement; assign feature to people.
When we have a full list, I'll setup some polls or something so we can
vote on desirability and feasibility. This is also a good time to
start discussing current proposals, and if people think it would be
helpful, we could schedule a skype call to discuss in detail.
Thanks for your interest!
-Dan