ARB (Architecture Review Board) & JSR (Java Specification Request)

OK here’s a quick sum-up of what drives me to start this thread :

  • It seems that Xith3D has been developed very quickly (I’d say, in a “rush”) by David Yazel for his game, Magicosm
  • Some people have been interested and added features (Yuri VI. Gushchin, Java Cool Dude, Artur Besiadovski and others)
  • There was no code conventions, nor real reviews/testing/validation of the added features
  • Some features have been broken along the releases (ex : collision system, xith gui)
  • Small packages have been added everywhere
  • Some classes aren’t javadocumented at all
  • Xith3D’s architecture is now “hard” to understand, and you need a real work to know how the whole system works

So from what I understood the ARB (Architecture Review Board) is a bunch of competent people that review any changes of the project, feature adding, and who looks for the best way to implement something, that maintain documentation, that ensures that changes are conform to the original vision of the project.
With my very little experience and my pretty small knowledge, I think it’s a good thing to have, but heh we have to group the competent people together, right ? And my questions are : “How is it organized ?”, “How do the ARB communicate ?”, “What’s the procedure to add a feature ?”, and all that things…
To me, some names comes to my mind for the ARB composition :

  • William Denniss
  • Jens Lehmann
  • Yuri Gushchin
  • Kevin Glass
  • Artur Biesiadowski
  • Abdul Bezrati
  • Arne Müller
  • David Wallace Croft

I wouldn’t mind participate to it but it would be for learning purpose and it’s to you to judge if I would be useful or not.

About the JSR (Java Specification Request), it’s a part of the JCP (Java Community Process, see http://www.jcp.org) it seems to me the “formal” way to make a good lib ^^ Of course it doesn’t avoid to work a lot, but I think Xith would gain more visibility and professionalism.
Do you think it’s a good idea to send a JSR for a game-oriented scenegraph ?

I prefer the informal way.

Xith engine is not so hard to figure out (took me less than a day to get a good idea of the internals), and not big enough to start playing with comitees and JSR.

What is really needed is better documentation (API, getting-started, demos, test cases for every feature), than we can go a step further and refine/extend the engine. This is the only way to attract new game developers around (reduce the steep learning curve).

I like the way it’s done now : contribution to the toolkit when adding non-core features, and open discussions in the forum when someone wants a new core feature.

An improvement would be to define ‘milestones’ and try and reach them, but I’m not sure there’s enough people around to go into that direction right now…

Lilian :slight_smile:

Ahah, I see.
So really the doc work is the way for me to go. And code cleaning of course, but I’ll have to wait until I have Developer access on xith core CVS (Will, please ?).

about the test case thingy …
i believe it is not that easy to create a test suite for a 3d rendering package …
at least you can’t do something like:

assert( renderedImage, testImage )

to determinate if both look the same, or am i mistaken there?

does anyone know how to create testcases for xith?

Hi,

[quote]but I’m not sure there’s enough people around to go into that direction right now…
[/quote]
I have to agree, unfortunately…

[quote]but I’ll have to wait until I have Developer access on xith core CVS (Will, please ?).
[/quote]
Apply for developer access and I will grant it. But PLEASE - do any of the code cleanup with a great care! There are other people around, so it is better to have changes committed with small chunks and wait while other people who use sources merge with their own changes (or migrate).

And please no incompatible changes right now.

Yuri

Yes I know. At least I have a small idea : you have a testcase suite and for each testcase a little window pop-up and asks you if what you see is conform to a small description. That could be enough, I think.

I have to agree, unfortunately…
[/quote]
Well, that’s just a matter of time…

Apply for developer access and I will grant it. But PLEASE - do any of the code cleanup with a great care! There are other people around, so it is better to have changes committed with small chunks and wait while other people who use sources merge with their own changes (or migrate).

And please no incompatible changes right now.
[/quote]
Thanks Yuri. So the wiser for me would be to ask the permission to make any change ? Actually I’m thinking of refactoring/splitting/adding classes to the com.xith3d.test package. May I do ?

Hi,

[quote]Actually I’m thinking of refactoring/splitting/adding classes to the com.xith3d.test package. May I do ?
[/quote]
Sure.

I even think it should be factored out of xith3d.jar - I personally use custom minimalistic Xith3D build with a lot of classes stripped out.

Yuri

Sure.
[/quote]
OK.
So I’ll reorganize testing when I’ll find time for that.

I agree.
But we should adjust the build.xml file to pack these files in something like xith_test.jar

Oh, there are testing classes in com.xith3d.render.lwjgl.test… I’ll move them to the new testing package.