Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Possiblility to select a robot in Bundles #14

Open
saarnold opened this issue May 6, 2015 · 3 comments
Open

Enhancement: Possiblility to select a robot in Bundles #14

saarnold opened this issue May 6, 2015 · 3 comments

Comments

@saarnold
Copy link
Contributor

saarnold commented May 6, 2015

I think this would mainly affect the config directory and the transformations that should be loaded in the bundle initialization. Does something speak against implementing a support for robot sub directories in bundles?

@doudou
Copy link
Member

doudou commented May 6, 2015

Depends on how it is done. I would be OK with having an equivalent of the (new !) Syskit mechanism for the script-oriented bundle support for instance. Which means having a config file in config/robots for the bundle system to load. That file does all the setup needed (nothing implicit anymore)

@saarnold
Copy link
Contributor Author

saarnold commented May 6, 2015

How would this config file look like? I assume this would then also be used in the Robot.config block in the config/robots/robot_name.rb. Or should bundles load directly the robot_name.rb?

@doudou
Copy link
Member

doudou commented May 7, 2015

.That is ... a very good question.

I would definitely prefer having two files, one for syskit, one for orocos.rb / bundles. Otherwise, one could easily add some syskit-specific stuff and break the orocos.rb/bundles things (and vice-versa)

However, naming-wise, I wonder what would be best ..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants