[Rock-dev] vizkit ruby will be moved out of gui/vizkit

[Allan E. Conquest]

Am 29.11.2012 15:14, schrieb Alexander Duda:
> On 11/29/2012 03:03 PM, Allan E. Conquest wrote:
>> Am 29.11.2012 14:48, schrieb Alexander Duda:
>>> Hi,
>>>
>>> gui/vizkit/ruby will be moved out of gui/vizkit as the ruby part is
>>> completely dependent on rock which is not the case for the c++ part.
>>>
>>> What does that mean?
>>> * we need a new repository for the qt ruby rock stuff maybe "qt_rock"
>>> would be a reasonable name. Any opinions on that?
>> I would prefer naming it something like 'qtruby' or 'rock_qtruby'.
>> 'qt_rock' would be ambiguous because you might think all Qt stuff is
>> only there.
> This is kind of intended. I don't know if it makes sense but the idea 
> is that every qt gui for any rock component should use this package. 
> Having a qt gui directly embedded in an orocos task context is
> no longer recommended.
>
> Alex

Then maybe 'qt_base' or 'rock_qt_base'? Generally, I prefer not to name 
folders 'rock_xyz' because it should be clear that we are using rock.

>
>>> * The hole history for gui/vizkit/ruby will be extracted and moved to
>>> the new repository. The files in gui/vizkit/ruby will stay until the 
>>> new
>>> repository is completed and tested. Any changes to gui/vizkit/ruby from
>>> now on will be merged to the new repository before gui/vizkit/ruby will
>>> be deleted. But keep in mind that any change will most likely result in
>>> a merge conflict as the code will also be updated to use the new
>>> orocos.rb async api instead of OQConnection and port_proxy.
>>>
>>> Greets Alex
>>>
>>>
>> _______________________________________________
>> Rock-dev mailing list
>> Rock-dev at dfki.de
>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
>
>