new Odejava release - grab it while it's hot

Game Mechanics
#1

Hello,

I have released a new version of odejava with new binaries and also an updated webstart extension.

This release includes many code and javadoc improvements from Justin. I also upgraded Odejava to use the latest ODE sources (from CVS) and the new methods added to odejava.i a while ago (including setting the random seed) are now accessable in Odejava.

Post any issues with this release in this thread please.

Cheers,

Will.

#2

Two notes regarding Justin’s changes:

  • Space is now abstract - replace all instances of Space with HashSpace in your code. Other types of spaces are also available.
  • JavaCollision now needs a World passed in its constructor. This is for future support of multiple Worlds.

Your code will not compile without these changes being made first.

Will.

#3

nice one Will and Justin :slight_smile:

#4

Woohoo! ;D

My next focus of the development cycle will be to abstract the logging system to remove the hard dependence on log4j, while allowing other options. Not sure yet, but this work may also include some prototyping stuff that I’d been working on that allows abstracted ODE native interface work so that there’s a debug version of the internal interface as well as the normal one. The other focus will be for allowing multiple simultaneous worlds to function. A lot of our Xj3D users will be needing this capability, so it’s coming fairly soon (though probably far less relevant for game developers, it’s been a major impediment to us doing some of the more advanced content we’ve been wanting to).

#5

Could we work together on this? I too have this on my near term list before the release of Typhon/Auriga in December. I will be ODEJava space Jan/Feb… soon… :slight_smile:

#6

Can do. I’ve already sent Will a set of classes that we’re using for a number of projects that he is happy with for the basic design. If you’ve seen the ErrorReporter interface from either j3d.org or Xj3D, then you’ll see what I’ve proposed doing. There’ll be a new package for logging - org.odejava.log that everything will go into.

Fire me an email (it should be available directly here) and I can run you through everything we’ve got so far. My initial plans were to put in loggers for Log4j, java.util and stdout.

#7

[quote]Can do. I’ve already sent Will a set of classes that we’re using for a number of projects that he is happy with for the basic design. If you’ve seen the ErrorReporter interface from either j3d.org or Xj3D, then you’ll see what I’ve proposed doing. There’ll be a new package for logging - org.odejava.log that everything will go into.
[/quote]
I am curious if this generic logging facility will be separate of the ODEJava package. I’m sure that is your intent and specific ODE interface code to this facility will be present in org.odejava.log

I have sent you my email via PM as I couldn’t find yours in your profile, etc.

This sounds good for sure and of course not duplicating work always helps especially if enough projects start to use the generic logging facility. Perhaps creating a separate org. hierarchy would further help the goals of the project.

#8

Uh, guys. I’m probably late in saying this, but doesn’t Jakarta Commons Logging do exactly that? (abstracts logging kits while supporting Log4j, Java 1.4 logging, etc…)

#9

Is there a changelog, for both odejava and for the natives?

Regards