Just in case anyone who is reading this is wondering what the hell these
guys are talking about, I'll highlight it very simply:
> keyFrames[0] = new TCBKeyFrame();
> keyFrames[0] = keys[0];
Note that the keyFrames[0] object is being assigned twice in two lines.
The first line creates a new instance of the object. The second line
throws away that newly created instance and replaces it with a
_reference_ to the object from the incoming array. The just created
object in the first line has never been used so we are dealing with a
big performance hit of creating a new object and then having it
immediately garbage collected. This is not isolated to one case in the
j3d utils package either.
Now, back to Andrew's original point about source etc. Over the years of
working with Java I have serious doubts about the competance of many of
the core Java team. It's either they are just really bad at programming
or they have management breathing so far down their necks to get the
next new set of functionality out the door that they don't have time to
do anything other than kludgy coding. Another potential problem is that
nobody seems to be in charge of an entire architecture. My favourite
topic of Java's image loading is a classic example of this where nobody
seems to know what anybody else is doing. On one hand there is this
perfect system called URL content handlers then we have the toolkit code
and finally the rendering code, all of which need to take separate
copies of the data blowing memory usage out of the water. This goes back
to even little things like naming conventions - Point3d vs Transform3D
for example - and this done by people working on the same project!
Freely available source that we could modify unhindered would solve many
of these problems. Peer review is a wonderful thing for dealing with
getting bugs ironed out.
--
Justin Couch Author, Java Hacker
Snr Software Engineer [EMAIL PROTECTED]
ADI Ltd, Systems Group http://www.vlc.com.au/~justin/
Java3D FAQ: http://tintoy.ncsa.uiuc.edu/~srp/java3d/faq.html
-------------------------------------------------------------------
"Look through the lens, and the light breaks down into many lights.
Turn it or move it, and a new set of arrangements appears... is it
a single light or many lights, lights that one must know how to
distinguish, recognise and appreciate? Is it one light with many
frames or one frame for many lights?" -Subcomandante Marcos
-------------------------------------------------------------------
===========================================================================
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".
