Rapps feature/issue prioritisation

[stonier]

@bit-pirate, @jihoonl

Since we're now collecting a fair bit of information on this, I thought I'd keep track of things here.

• Rapp Definitions
  • [x] relative paths to rapp internal files (interactions, public_interface): https://github.com/robotics-in-concert/rocon_app_platform/issues/231
  • [x] add type information to public interfaces, (needs an issue) #244
  • [x] add specification for public parameters, #170
• Rapp Manager Implementations
  • [x] implement parameters by exposing roslaunch args, #170
  • [x] expose rapp implementation information: #226
  • [x] preferred, not highlander policy for execution of rapps, allow multiple rapp implementations with the same parent, #187, #230
• Other
  • [x] redefine teleop rapp: https://github.com/robotics-in-concert/rocon_app_platform/issues/224

[bit-pirate]

None of the issues linked above are urgent (IMO) and hence can be postponed to after the demo

[stonier]

Ok. Update here if you come across any showstoppers and I'll tackle them.

[jihoonl]

Bug label?

[bit-pirate]

Bug label?

Removed. The above issues are either results of design decisions or enhancements.

[jihoonl]

For the record,

All the rapp attributes except parent_name will get relative path after resolving #231, we have decided not to use / based resource finder.

[jihoonl]

All done!