----- Original Message -----
From: "Fergus Murray" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 16, 2001 3:44 AM
Subject: Re: [JAVA3D] TransformGroup & Transform3D
> But this is really my problem: To my mind, the Transform3D is an integral
> part of the TransformGroup concept. It's hardly a transform group if it
> doesn't have a transform, is it? It's just a group. So putting them
The "have" verb you used is important: a transform node HAS-A transform matrix.
A transform matrix is a part of a transform node. While it's true that every
transform group has a transform, not all transform matrices are part of a
transform group.
It would also be possible for an alternate design to say that a transform node
IS-A transform matrix, but that would require multiple inheritance of
implementation, which is frequently poor design and isn't supported in Java. And
for these two particular classes, because of their large interfaces, it would be
especially ugly and difficult to understand and maintain.
> Still, I guess the fact that Transform3D has potential uses independent of
> the Group node means that it makes some kind of sense for it to be a class
> of its own - even if it would have been perfectly possible for a single
> Transform class to do exactly the same things.
Providing only transform nodes would require users of transform matrices to use
scene-graph transform nodes, which they might not want.
===========================================================================
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".
