Sometimes it helps to have some distance from the code. After a weekend without any coding I have found the "last" bug in QuickStepper. All tests are running now with QuickStepper and show pretty reasonable results.

Sometimes it helps to have some distance from the code. After a weekend without any coding I have found the "last" bug in QuickStepper. All tests are running now with QuickStepper and show pretty reasonable results.

Regarding the webpage effort: What about using apache forrest (http://forrest.apache.org) for the webpages? It is very simple to create some static webpages with forrest using XDoc. If there are no complaints I would start setting up the project to use forrest for the webpage.

Regarding the webpage effort: What about using apache forrest (http://forrest.apache.org) for the webpages? It is very simple to create some static webpages with forrest using XDoc. If there are no complaints I would start setting up the project to use forrest for the webpage.

I have setup a documentation structure with Apache Forrest and checked in the doc.

Until now Apache Forrest (http://forrest.apache.org) has to be installed on your computer to build the website. If you have setup Apache Forrest the site can be generated by running the command forrest from the projects root directory. The generated site then can be found in the directory build/site.

mmh have you changed anything at the steppers, hdietrich? Because now the BoxBoxCollisionTest looks real crazy, but I think, it looks also a bit wrong with the QuickStepper. mmh...maybe theres something more general wrong...or is there maybe accidently an old version up?

Uh, you are right. The BoxBoxCollisionTest and BoxCollisionTest show ugly results. The rest of the tests are OK, at least the one's that were working before. I have the suspicion that the BoxBoxCollider still has errors.

The Stepper were not influenced by the last changes, so I think it's not realted to the API changes I just commited. I will do some debugging of the BoxBoxCollider again

I just wanted to see what the state of JOODE was and so I attempted to compile the latest code from Subversion (rev 234). It fails to build, assuming simply issueing "ant" in the same fodler as the build.xml should work.

Can you please point me to the real code repository of joode? I have looked at joode.dev.java.net cvs, but the sources are untouched for nine months. And can you tell me the current development status. What is missing? Is there a roadmap?

I've nto been active in JOODE for a while, but am taking another look at it. I noticed that JOODE currently is using JOGL 1.1 for examples, which is casusing a lot of problems when I try to run them against the new JSR 231. Would it be okay iwht the admins if I upgraded the test code to run with JSR 231?

I've nto been active in JOODE for a while, but am taking another look at it. I noticed that JOODE currently is using JOGL 1.1 for examples, which is casusing a lot of problems when I try to run them against the new JSR 231. Would it be okay iwht the admins if I upgraded the test code to run with JSR 231?

For me the link ends in a page-not-found-error for some strange reason. But if I directly typed it into the address field of my firefox it worked. But you can easily go to xith.org and click on features->Development Plan and you'll see the plan .

You guys migrated you source to sourceforge some time ago, didn't you? Did you have to pay dev.java.net for handing out the RCS files? As far as I know they're needed to migrate the CVS history, aren't they? If you made it a free way, please tell me how you did it.

java-gaming.org 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‑gaming.org