[Rock-dev] Patch "add --prefix" to Roby

[Chris Müller]

Hi Sylvain

i've implemented now an easy combination of both approaches:
First it's possible now to add the "robot_type" to the commandline arguments
for each deployment as :prefix => "robot_type" option pair.

I'm sure this feature is not always wanted for other robotic systems. 
Therefore
its necessary to activate it within config/app.yml by adding:

robottype_deployment_prefix: true

Of course, It's also possible to add the "robot_name" to the prefix 
argument.
But i only use the robot_type first for now  because the name is also ofteny
used for a distinction for the real system and its simulation. Therefore
Prefix-IDs e.g. in form of "simulation_0" is probably not wanted for the
FAMOS/Communication Components. I guess, we would need an additional 
convention for that within
the FAMOS/Communication sources that uses this prefix.

All changes are only present in Orocos.rb. If nobody complains, i can 
push my changes to master
or use another branch :].

Chris


On 08.08.2011 14:10, Sylvain Joyeux wrote:
> Roby *is* and *must* remain independent of Orocos. Ergo, you cannot 
> add this --prefix argument to scripts/run.
>
> If you need such an argument, the standard mechanism (for now) is to 
> add it to the app.yml in config/. It is possible to add it in a 
> robot-specific section.
>
> Alternatively, you could use the fact that, in Roby, there are two 
> names involved: a robot "type" and a robot "name"
>
> I.e. you could just make the prefix
>
>   #{Roby.app.robot_type}_#{Roby.app.robot_name}
>
> This way, one would do
>
>   scripts/run crex chris
>
> Get the common config for "crex" and have the naming be crex_chris_blabla
>
> Sylvain