Roadmap

From The Player Project

Jump to: navigation, search
 
Line 9: Line 9:
* Player: Alternative transport methods. Make Player able to be used as client/server, or as a distributed architecture (see [http://www.is.aist.go.jp/rt/OpenRTM-aist/html-en/ OpenRTM]).   
* Player: Alternative transport methods. Make Player able to be used as client/server, or as a distributed architecture (see [http://www.is.aist.go.jp/rt/OpenRTM-aist/html-en/ OpenRTM]).   
-
 
+
* Player: Clean up documentation. Make sure all config file options are documented, and all configuration requests are listed.
-
* Gazebo: Collada format support (Visual and Physics) in Gazebo. This includes being able to load entire scenes and individual modles from collada. It also implies changing the current loading and saving XML methods to be a general import/export from some kind of format manager. As a cool extension, Gazebo can connect with the models of Google Earth, as a library available to the user for instance, because they are saved in Collada format.  
+
* Player: Verify all drivers use lengths and angles from config files internally.
-
 
+
* Player: Compile all drivers a plugin drivers, install to common subdirectory in libdir. Write parsing code that finds all driver names. Leave shell drivers in libplayerdrivers
-
* Gazebo: The basic infrastructure is there but a GUI is needed for building worlds. A GUI and some features as better navigation in the world, 3d picking and moving objects are needed to make a build worlds GUI. The GUI can be used to change the properties of the objects in the simulation, add new models, add controllers to the models, etc. This work is independent but can benefit from the Collada support idea above.
+
= Player Development Roadmap =
= Player Development Roadmap =

Latest revision as of 02:30, 1 January 2012

Personal tools