The big quesion is - how many people are actually using the community builds anyway?

I will keep them up todate but I need to know how frequentally to do it. If only people who are trialing Xith (and switching to CVS if they continue using it) are using them then I will just do it once every month else if there is demand I can update them every time a significant feature is added / bug is fixed.

I may also start to remove old releases which were not flagged as a significient milestone (eg. Alpha5). Any objections to that?

I'm new to this forum but I've been watching your progress for the last 2 months.You're doing a great job!

Now, back to the thread.I think it will be good to keep the builds up to date frequently (twice a month may be) because I think there's people who are hidden behind firewalls and it is very difficult (impossible for me) to get CVS working.Now if I'm the only one, then un update every month will do.

I think a new build should be released once approx. a month has passed _or_ there is a larger update. Larger updates are Behaviors, collision detection/avoidance etc. The criteria should be that every app presented at xith.org can be run with the latest community build. I think there's no need for you to release a new build for every solved issue or minor update. A download link for the current Javadoc could be handy for some people.

Besides this I think that there should be a either a new official release or a link from the Xith3D home to the community builds. I know of two people who tried to run apps using the official release, which doesn't work in most cases, because it's too old.

Just a quick word as I am about to go out - if anyone wants FTP access to be able to upload builds - just email me. To create a community build it's as simple as "ant cbuild". A ChangeLog is a good idea - why don't we make a sticky ChangeLog/Release thread in these forums?

As for the official xith project home page I think a link to xith.org would be good for new users.

http://xith.org/download/builds/I think foldernames should follow YYYY-MM-DD_xyz naming convension to be sorted properly. Currently, builds folder is very hard to see whether there are new downloads avail.Especially non-native english people have sometimes difficulties to put three-char month names listed.

I have updated it. http://xith.org/download/builds/?N=D

"_cvs" indicates that the build is a snapshot and is not nessesarily tested or relyable. "_alpha8" or somthing similar means that it is a milestone build and should be slightly more dependable.

Regarding the ChangeLog - the options that I see are:* ChangeLog file in CVS* ChangeLog thread in the forums* ChangeLog file on some web site.

the CVS options is probably the best I think.

I think a sticky "releases" thread is probably a good idea for when community builds are updated.

We are now adopting the policy that xith3d.jar should NOT belong in jre/lib/ext (see the above tute for explanation). The cons far oughtweigh the pros (the only real pro is conveniance but infact it is very inconveniant in some situations).

I'm happy to announce a new section in the Getting Started Guide about Swing Integration.

The app is a framerate counter with an (optional) exit button. It uses the hidden high-resolution-timer of JRE 1.4.2 (because of the lack of an official timer in Java) and shows the use of UIWindow. An advantage of the tutorial is, that you can plug the counter in your existing games/demos by adding just one line. It's a long tutorial, so you need some free minutes to read through it.

This is also the first time the Getting Started Guide is build directly from xith-tk CVS, so a lot of things have changed internally. If you notice mistakes, please inform me. (You may have to clear the GSG demos from your webstart cache, if webstart doesn't work.)

Don't know if this issue was already noticed, but there are problems with the MouseListener, when the window is resized. You can test this by starting the webstart version of the tutorial and clicking on the exit button.

Is re-calling setRoot() on a UIWindow still the only way to mark the component as completely dirty? It just didn't feel like the final solution.

It's good you mention this. I noticed this, when I wrote SwingFPSCounter, but forgot to write about it in the forum. Currently I don't know a better way to mark the component as completely dirty. If no one else knows, I'll submit this as an issue.

Regarding the window-resizing: I found out that adding

1

canvas.get3DPeer().getComponent().setFocusable(true);

solves the problem. However I don't know if that's obvious. What do you think?

Yes, I too think so. :-) I like your tutorium.The Swing/Awt to Xith3d relation is interesting: not only the usage of Swing components (painted via Jogl) inside Xith3d Canvas3d, but also when Awt/Swing components sits next to a Xith3d Canvas3d. For example if your game/whatever runs in a window and you hit some Swing buttons in order to open JTable data editors or that like...

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