[Rock-dev] MARS goes Rock

[Jakob Schwendner]

On 11/30/2011 06:28 PM, Alexander Duda wrote:
>
> On Wed, 2011-11-30 at 16:37 +0100, Malte Römmermann wrote:
>> Hey,
>>
>> we are going to extend rock with some simulation libraries. Some of these libraries currently have rather unfortunate names so we also want to take this opportunity to rename some of them. The following list includes the libraries with their current library names, a proposal for new names under which they would go open source and a one sentence description for each. We are not that creative concerning the library names, so if you have suggestions we are open for discussions. ;-)
>>
>>
>> lib_manager ->  lib_manager
>>   - allows dynamic loading of libraries and gives access to the libraries
>>
>> cfg_dfki ->  cfg_manager
>>   - loads and saves configuration files using yaml-cpp and gives access to configuration parameters
>>
>> data_broker ->  data_broker
>>   - a library to simply exchange data between different independent moduls/libraries, including a timed callback handling of producing and receiving data
>>
>> gui_core ->  main_gui
>>   - a class implementing a QMainWindow with an interface to extend the menu, toolbar, and to add QWidgets to the gui
>>
>> mars_core ->  mars_core
>>   - basic library for MARS including MARS data types and enums
>>
>> mars_graphics ->  mars_graphics
>>   - includes the 3d graphics implementation of MARS
>>
>> mars_sim ->  mars_sim
>>   - the simulation library itself, which can also be used without any gui (to load meshes there is still a dependeny to mars_graphics, we are going to remove that one soon)
>>
>> mars_gui ->  mars_gui
>>   - a bunch of qt widgets to control the simulation and access the simulation data
>>
>> mars_app ->  mars_app
>>   - installs a binary, loading the MARS libraries to use MARS as standalone application
>>
>> console_dfki ->  log_console
>>   - a qt widget to print messages piped through the data_broker
>>
>> gui_cfg ->  cfg_manager_gui
>>   - a qt widget to access all configuration data
>>
>> data_broker_widget ->  data_broker_gui
>>   - a qt widget to access all data known of the data_broker
>>
>> ode ->  ode_mars
>>   - currently we use a patched version of ode, if we include the patch into our build process (autoproj) we don't need this library. Maybe I also get along without the patch, I will check that soon.
>>
> thanks for doing all the restructuring.
> I also would suggest to create less repositories for it:
>
> * one for the simulation related stuff (we do not have support for other
> engines so far)
>    * ode ->  ode_mars
>    * mars_sim ->  mars_sim
>
> * one for the gui of the simulation
>    * mars_gui
>    * mars_graphics
>    * mars_app
>
> * one for qt widgets we can share between mars and rock in the future
> (replace vizkit main window)
>    * console_dfki
>    * gui_core
>    * gui_cfg
>    * data_broker_widget
>
> * one for libs which are not depended on qt osg etc.
>    * lib_manager
>    * cfg_dfki
>    * data_broker ->  data_broker
>
> (maybe we can discuss this on Tuesday)
>
> Back to the naming I would also add widget to the most gui related
> packages (some suggestions)
> gui_core ->  main_window_widget
> mars_gui ->  mars_core_widgets
> data_broker_widget ->  data_broker_widget
> mars_graphics ->  mars_osg_qt
> gui_cfg ->  cfg_widget
> console_dfki ->  log_widget
>
> Alex
>
I agree with most of this, and also that it's probably best to discuss 
this in person. (Maybe on Rock-Friday?)
I think it would be really helpful if Malte could sketch the use cases 
that he has.
I think in this way we can find practical divisions, that may not take 
up so many repos/libraries. Alex's suggestion is a good starting point 
for this.

cheers,

Jakob