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
We can execute some demos as apps with this app_manager. But sometimes there are many procedures to do demo. For example, when we want to diabolo demo, we have to know what we prepare(designated diabolo and its sticks), how PR2 hold sticks(with our help? or not), ...
So I think that each demo there should be a doc to write what we prepare, what to help or what to attend when executing demo. I want each app have doc.md, and we can read it with rosservice like rosservice call doc_app diabolo or with raw markdown file. With this, one who is not so new to one demo, he can execute it with this doc.
The text was updated successfully, but these errors were encountered:
This is such an awesome demo! :D
I'm not sure how helpful such a service call would really be.
For a graphical app manager a text that is automatically displayed for the app might make sense.
I believe it is very challenging to give enough information in such a text so someone else might perform the demo without being instructed.
Photos would simplify this a lot, but then you require full html-support (or interpreted markup) which makes more sense outside the ROS system.
So I would propose to leave this out of the app manager itself, but encourage you to write good documentation in rosdoc/[rosdoc_lite](http://wiki.ros.org/rosdoc_lite).
We can execute some demos as apps with this app_manager. But sometimes there are many procedures to do demo. For example, when we want to diabolo demo, we have to know what we prepare(designated diabolo and its sticks), how PR2 hold sticks(with our help? or not), ...
So I think that each demo there should be a doc to write what we prepare, what to help or what to attend when executing demo. I want each app have doc.md, and we can read it with rosservice like
rosservice call doc_app diabolo
or with raw markdown file. With this, one who is not so new to one demo, he can execute it with this doc.The text was updated successfully, but these errors were encountered: