This post isn't meant to pressure Will and Jani, but meant as a place to document obvious missing functionality in the odejava binding. On a personal note, these items are holding me up, but hey, no pressure
Hey, ideas are always welcome!
1) Multi-geom support within a body. Need the ability to add mulitple geometries to a body, each with their own translation/rotation relative to the body's reference point.
This should already work on Odejava, although only on Low Level, William is doing work with High Level API.
2) Ability to remove a Body from a World. There is, of course, a way to add a body, but no way to remove one.
This is because how ODE works, and may I say ODE's own API is pretty wierd from some places. There is no way to remove body from a world. Also when creating a body you have to add it into a world same time which later cannot be changed, in other worlds when you create an body on ODE, worldId is required parameter.
3) Ability to remove a Geom from a Space. Like bodies in a world, I need to way to remove geometries from collision space.
This already works, however I do not remember if it's added to Higher Level API? Now that I checked the source code I see that William has already added this method to Higher Level API also.
4) DisplayTransformable.setTransform method should probably have an additional parameter: the OdeTransformable the DisplayTransformable is associated with in the DisplayBin. This would allow a single class implementing the DisplayTransformable interface to handle multiple objects. This isn't important for me now, but more a matter of Java form.
I'll let William to handle this, perhaps now it's already fixed?
On a related note, I'd be happy to contribute to the odejava project (instead of just whining). Should I get CVS write access or should I just post diffs to this forum?
You can post patches here first, then ask for developer status if it seems that you really want to participate and do commits every now and then.