Hi
I guess and I say _guess_ that the API and future shape of Gazebo is still
not
defined to spend time in this kind of documentation. Better spend time
developing.
Anyway to free Nate from all the work, what about using the player-stage
gazebo wiki to put this information together?
The developing process have many steps, you can't (shouldn't) write a
program if you don't know where do you want to go. Take a look at
http://en.wikipedia.org/wiki/Software_design .
I don't want a book about "the future of gazebo", only a *little*
explanation in order to discuss wich are the best solutions.
Maybe some information on the current syntax of the world file to let some
people start testing their own worlds even when this syntax may change in
near future.
I don't think people want to do twice the same work.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Playerstage-gazebo mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo
