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
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?
The text was updated successfully, but these errors were encountered:
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)
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?
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 ..
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?
The text was updated successfully, but these errors were encountered: