[Rock-dev] [Syskit] Naming convention for ruby task contexts

[Sylvain Joyeux]

On Wed, May 6, 2015 at 10:38 AM, Malte Wirkus <malte.wirkus at dfki.de> wrote:
> 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::

>
> 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.

I thought about it, but then it would mix the files that are
extensions to the C++ orogen components and the files that are pure
ruby tasks.

Or we could go for

   orogen/rtt
   orogen/ruby
   orogen/ros

which actually looks pretty nice