On 30.04.2015 18:00, Sylvain Joyeux wrote: > One can now create pure-ruby task contexts, i.e. components that do > not have an underlying C++ component written with oroGen. It is used > in Syskit mainly for testing and for simple tasks (such as components > that periodically write always the same value). > > > So, where should it go ? ruby_tasks would be awkward as it can be > understood only in the context of syskit (in the general Roby context, > Roby tasks are ruby tasks ...). ruby_components ? > > My proposal: put them with the Roby tasks in Tasks:: > > Sylvain
If I understood correctly, the task context provide an implementation of the oroGen Task model. That makes the models/orogen subfolder (with corresponding namespace) also a good option. Malte _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
