Daniele Dellafiore wrote:

> What is the status of j3d.org code? The version 0.6 is dated february
> 2002. What improvements, if any, have been done to the code since that
> date? Is actual code enough stable to try to use it?

As stable as any beta code can be :) Seriously though, almost all of the
code in the codebase is getting used on a daily basis in our project
work. If something doesn't work we fix it really quickly. However, we
may not exercise every option of every piece of code, so there could be
stuff that has bugs in it or features that are not supported yet
(because we haven't had the need for support).

As for stable releases I actually tarballed everything a couple of
nights ago to put up onto the site. I was intending to make that 0.7 but
I haven't had a chance to do some regression testing on the code to make
sure all the example code still works. Thus I haven't tagged CVS and
made it official yet. If you would like, I can send you the zip files as
a private email or stick them on the FTP site for you to download.

> some people, trying to creating a small community of developers. Is that
> right? Are you still working in that direction?

I assume so. We (Yumetech) have expressed some interest in being part of
that, but our lazy arses haven't filled in the paperwork yet because
we've been doing so much else....

> There are any interesting news, after Siggraph 2002, about the OGL 2.0
> porting for Java? I remember Justin was talking about very important
> changes that are on the way, and that after SigGraph we could have known
> more about those... Feel free to tell me (us) all gossips about these
> arguments :)

Currently we're in a holding pattern while the various groups get their
shit together. Alan was down in SF yesterday attending the kick-off
meeting of the Khronos group efforts under their new working regime. It
is through them that we're going to be doing most of the Java OpenGL
work. It's going to be a little bit of a while before you see full OGL
2.0. Khronos is only directly interested in the Embedded OpenGL
specification, which is basically a profiling/subsetting activity of OGL
1.3. That's what we're being initially funded to work on. However,
during the Siggraph meeting, about half the ARB members, including the
head of the ARB were there as well. They grabbed us at the end of the
meeting and verbally stated "if you do it, we will bless it. We've been
wanting this for a long time" and then gave us a potted history of the
efforts to date. That's great from our end, but we're lacking a bit of
manpower to pull it off in a short term, so we're concentrating on the
ES spec first and then broadening to the larger work of 2.0. Perhaps we
can encourage others to work on it too, but we need to get the base in
place first. Our initial thoughts are to fork GL4Java for this purpose
(fork because Sven has indicated many times he is not willing to put
GL4Java through any spec process, nor take any modifications from
others), but at least part of me wants to do it from scratch and put a
X11-style license on it so that everyone can embed our work in their
hardware.

--
Justin Couch                         http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler              http://www.yumetech.com/
Author, Java 3D FAQ Maintainer                  http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
                                               - Greg Bear, Slant
-------------------------------------------------------------------

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to