Kevin Rushforth wrote:
> Using RELATIVE_TO_SCREEN should do what you want. Btw, we have
> considered adding a variant of RELATIVE_TO_WINDOW that isn't centered
> in X and Y--similar to RELATIVE_TO_SCREEN, but with the manual X and Y
> eye position being relative to the lower left corner of the window
> rather than the screen.
OK, bitch time :) Why is it that Java3D always seems to want to do
things differently to every other Java API? This is a good example of
it. Why would you consider doing it relative to the bottom left corner
and not the top left corner like every other Java rendering API?
The Java vision is based around having a consistent API in both
functionality and commonality across many different areas. For example,
where I need to add a listener to something, the behaviour is always the
same - I can't add the same listener instance twice, or, I can
definitely add it twice (multiple) times. There is not a 50/50 mix of
some APIs only allowing a single add, while others allow multiple. Java
3D seems to consistently go against this trend.
One of the fundamental goals of the J3D API should be to maintain
consistency with the rest of the Java philosophy. By going against it,
you are making it harder for programmers to _easily_ adopt J3D into
their application. Now they need to re-learn everything for a special
case. Instead of a top left origin, they now need to deal with bottom
left, all their coordinate axes are up the wrong way. Having had to deal
with exactly this problem in native code in years gone by, I can
guarantee this will be a source of consistent and annoying bugs (having
negative signs all through things that need to be flipped).
Frankly, I don't care if having something in the bottom left of the
corner is there because it is simpler for the implementers to deal with.
It should be the job of the API to remain consistent with its
surrounding environment and make whatever "transformations" it needs
under the covers to deal with the underlying implementation specifics.
Try having to explain this illogicality to the new user and help them
having to debug it and you'll see what I mean....
--
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".
