[Rock-dev] MARS goes Rock

[Janosch Machowinski]

On 30.11.2011 16:37, 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
This sounds like a good candidate for a merge with gui/vizkit, which 
(guessing from your description) more or less provides the same 
functionality.
> 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
Hm, what about mars_widget or mars_widget_collection. That would match 
the existing naming scheme a bit better.
> 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
This sounds like everyone could use it. What about putting it under 
gui/console_widget ?
> 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
The old name, data_broker_widget, actually matches the rock naming 
scheme better ;-)
> 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.
> Best,
>   Malte
>
>
>


-- 
  Dipl. Inf. Janosch Machowinski
  SAR-&  Sicherheitsrobotik

  DFKI Bremen
  Robotics Innovation Center
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Phone: +49 (0)421 178 45-6614
  Fax:   +49 (0)421 178 45-4150
  E-Mail: robotik at dfki.de

  Weitere Informationen: http://www.dfki.de/robotik
  -----------------------------------------------------------------------
  Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
  Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
  Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
  (Vorsitzender) Dr. Walter Olthoff
  Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
  Amtsgericht Kaiserslautern, HRB 2313
  Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
  USt-Id.Nr.:    DE 148646973
  Steuernummer:  19/673/0060/3
  -----------------------------------------------------------------------