Hi !
Featured games (85)
games approved by the League of Dukes
Games in Showcase (615)
Games in Android Showcase (173)
games submitted by our members
Games in WIP (659)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  [Odejava] future enhancements  (Read 1221 times)
0 Members and 1 Guest are viewing this topic.
Offline William Denniss

JGO Coder

Projects: 2

Fire at will

« Posted 2004-04-15 10:24:25 »


I've now created issues in IssueZilla for all the improvements to Odejava that are currently on "my list" such as multi-geom support.  This is so their progress can be tracked and people can volunteer to do the coding to help me (anyone interested?).

A list can be obtained here



Offline Jani Laakso

Junior Devvie

Do it with Java!

« Reply #1 - Posted 2004-04-19 15:24:12 »


Currently Bodies can only be added to a world on creation.

Idealy they would be able to be created - then added to a world later.  This
means the contstructor arguments must be stored locally.  Unlike with Geom and
Space - I don't think they can easily be removed and added but can only be
created and destroyed.  This isn't a large issue except that their values will
need to be cached locally on creation and destruction.

ODE itself creates bodies with a World parameter which is mandatory. ODE public API does not support moving Bodies from a world into another.

You could defer object creation at the Odejava lowlevel side and separate Body creation from body.setWorld(worldId), but then you hit the problem that setWorld cannot be called another time.

So inheritly I'd go with ODE's own way in these cases. It's not pretty but it's simple. I wouldn't try to abstrahate ODE's own pecularities, ideal solution is something that ODE does not support. It's API is pretty wierd from some places (imho).


Currently, people using the High level API must still include the low level Ode
class for use setting and getting attribute of some Odejava objects (such as
Body).  Idealy these attributes would all have dedicated setters and getters.

This is not an API breaking change - legacy support can be kept (and possibly
deprecated).  A fair deal of refactoring is needed however.

Yep, this would be good to do. Also there's some obsolete SWIG classes that need to be removed.
Offline William Denniss

JGO Coder

Projects: 2

Fire at will

« Reply #2 - Posted 2004-04-19 21:56:36 »

I now agree with this too - we shouldn't run though hoops to do stuff ODE can't unless there is a compelling reason.  I'll invalidate that issue.


Pages: [1]
  ignore  |  Print  
You cannot reply to this message, because it is very, very old.

Coldstream24 (15 views)
2015-09-03 00:41:28

Andrew_3ds (24 views)
2015-09-01 19:08:10

afikri (16 views)
2015-08-31 09:30:22

afikri (24 views)
2015-08-31 09:30:07

afikri (13 views)
2015-08-31 09:27:24

afikri (16 views)
2015-08-31 09:26:40

Roquen (24 views)
2015-08-29 11:30:54

GamerC4 (34 views)
2015-08-22 20:38:50

GamerC4 (32 views)
2015-08-22 20:37:18

GamerC4 (37 views)
2015-08-22 20:37:01
HotSpot Options
by Roquen
2015-08-29 11:33:11

Rendering resources
by Roquen
2015-08-17 12:42:29

Rendering resources
by Roquen
2015-08-17 09:36:56

Rendering resources
by Roquen
2015-08-13 07:40:51

Networking Resources
by Roquen
2015-08-13 07:40:43

List of Learning Resources
by gouessej
2015-07-09 11:29:36

How Do I Expand My Game?
by bashfrog
2015-06-14 11:34:43

List of Learning Resources
by PocketCrafter7
2015-05-31 05:37:30 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!