Development TODO
From ODE Wiki
This is like a brain-storming page of specific TODO items of ODE developers. For a release based list, see the Feature Plan page.
- Get all collision primitives to collide correctly with each other (what is the status? See Collision Matrix in Features)
- Create a reference guide on the ODE API, to be generated with doxygen. We use a so called literate programming paradigm where documentation and source are at the same place, in the same file. We need to have all user-visible ODE functions/constants/datastructures documented using this system. A cron job runs doxygen each day, and puts the results at http://opende.sf.net/docs/ where users can view the reference manual. Doxygen control is in the ode/docs/Doxyfile file.
This article is a stub. We know this article will be useful, but no-one has yet stepped forward to fill it. You can help us by expanding it. 
