From: Matthias B. <ba...@ir...> - 2004-06-27 21:09:26
|
Timothy Stranex wrote: > I agree with Bernie: move the existing code to "pyode_previous" and put > the new code into "pyode". ok, done. I just noticed a slight disadvantage in reusing the pyode directory. There's the subdirectory "include" which isn't necessary anymore, however as cvs doesn't allow to remove directories it will remain there... oh, well. The text files README, INSTALL, etc. are still the old ones, they have to be updated eventually. Here's an incomplete list of things that still have to be done: - Check the ODE API for new (or so far unsupported) functions and add them to the respective class - Trimesh support - Add some __str__() methods that output useful data - Make the documentation (doc strings) complete. By the way, I noticed that the epydoc markup @param can't be used because epydoc doesn't see the argument names. Is there a way to get around this? - Add AMotor class - Add CylinderClass (not the capped one). Is that already officially available? There's no section in the docs, but it's mentioned as a geom type. - Do more error checking. Currently, it's still possible to crash the interpreter if you do "wrong" calls. - Review the design and improve whatever has to be improved (like the global lookup dictionary). - Make the objects pickleable? - XODE reader - Update all the files that are necessary for a proper release (readme, license, changelog, ...) - Add a proper file header on all the .pyx files - Write more examples, demos, tutorials. :) But at least the current version can be compiled and is fully functional. I hope it'll also compile on Linux. To compile you can just call "setup.py build" (by the way, as I've checked in the stuff on Windows the setup script won't have the executable flag set.... darn, and I believe now it's too late to change that in the repository. Oh, and you have to set the proper path to ODE in the setup script (the variable ODE_BASE)...) - Matthias - |