Bernie Roehl wrote:
> Perhaps we could update the instructions on the PyODE home page?
By the way, when doing an update the location of the repository doesn't
have to be specified again as it's stored in the CVS subdirectories. So
the third line on the above page could just be "cvs update" (from within
the pyode directory).
But maybe it would be enough just to refer to the original SF
documentation?
And while we are at it, when should we do our first "official" release?
I think the current state is almost ready for a release.
Here's the todo list from a couple of posts ago:
>New Features:
> - Add AMotor class
Done.
> - Add Cylinder class (not the capped one)
Cylinder is not yet part of the official API.
> - Trimesh support
An initial version that seems to work is in place. The interface for
passing the mesh data may be extended in the future.
> - XODE reader
It's finished as far as I can tell, isn't it?
> Review:
> - Check the ODE API for new (or so far unsupported) functions and add
>them to the respective class
I've added quite a few missing functions. There are still some more.
> - Review the design and improve whatever has to be improved (like the
> global lookup dictionary).
This has to be done yet.
> Cleanup:
> - Do more error checking.
Done sporadically.
> - Add some __str__() methods that output useful data
Not done yet.
> - Make the documentation (doc strings) complete
Partially done. Maybe this should be completed before doing a release.
> - Add a proper file header on all the .pyx files
Not done yet.
> Packaging:
> - Update all the files that are necessary for a proper release
>(readme, license, changelog, ...)
> - Write more examples, demos, tutorials. :)
Not done yet.
Even though some things are still missing I think we should try to get a
release out somewhen soon so that other interested people can give feedback.
- Matthias -
|
