Shawn, {smile} it's our passion for progress that prompts us to write
these comments.
I don't agree that Java 3D will die if it doesn't keep up (or catch up)
with the latest hardware and low level APIs (OpenGL & DirectX). It's a
matter of how you view the tool. If I want killer, cutting edge,
fastest possible 3D graphics I'll code directly to OpenGL or DirectX.
If I want to quickly develop a 3D application I'll use Java 3D.
This is almost the same disagreement I have with Dave (Yazel) about
MMORPG virtual world development. As a small company I don't expect to
compete with Sony/Verant or Microsoft for cutting edge high performance
3D graphics. But where I can beat them is using a tool like Java 3D to
develop a virtual world with better "rules" a heck of a lot faster and
cheaper (development time and costs - not performance). I can live with
inferior graphics and inferior performance... I just need it to be
reliable and easy to use (code).
So again (with passion and a friendly smile) I state again:
#1 - make it work (reliably)
#2 - document it so we know how to use it
and a far, far distant third:
#3 - add performance and new features
- John Wright
Starfire Research
Shawn Kendall wrote:
>
> Briefly :-)
> I will add this...
>
> The same old 3D issues pop up on the DirectX forums and game site forums
> as well. I still maintain that the greatest percentage is not Java3D,
> even if it's someone first attempt at 3D. If you go use the Image
> Processing APIs, you need to understand some image processing to get
> past "the wall" that comes from going beyond the examples apps...
>
> > It's like being lured into a calm, beautiful pool without warning that
> > there are sharks lurking under the water. We may be naive (and that is
> > our fault) but good customer service comes from addressing your
> > customer's needs not dismissing their problems as not your
> > responsibility.
>
> You have to drawn the line somewhere, don't you? I mean if I can't get
> the JDK install that's one thing. Not knowing how to use it is another.
>
> > I think we have over emphasized this discussion, but Justin's comments
> > like "Sun doesn't know what it's own code is doing" and "it's amazing it
> > works at all" were inflammatory. I don't think Justin was intending to
> > "flame" Sun (in fact he might have been complimenting Sun's Engineers in
> > his own outspoken, no holds barred manner). I think Justin was trying
> > to recommend to Sun the same thought that I feel - take a step back,
> > slow down, document and organize before proceeding with adding more
> > features. So I'll repeat my suggested priorities:
> > 1) Bug Fixes (reliable code)
> > 2) Documentation
> > 3) Performance tuning & new features (low priority)
>
> I very much disagree with the "take a step back, slow down..." part of
> above. Given the choice between having the team pause and build better
> examples and docs or improve the API, I'll take the API. The industry
> is moving FAST!!! Really fast. If Java3D doesn't get the nex-gen
> features in the API now, it's going to die. It's that simple.
>
> I say forget about us, and get out there and wrap those pixel and vertex
> shaders in DirectX and OpenGL in some OO architecture. Add extensions
> for the latest texturing capabilities and fix those bugs (BTW, the team
> is doing just this, thank you much!)
>
> While we on the list are moaning about better docs, the industry is
> leaving us in the dust. Work with the hardware people, so when the
> hardware comes out, Java3D team is already working on a mapping. Let me
> play catch up, but not the API. We are going to have to be fierce to
> make it out alive in the next few years!
>
> BTW, I do not mean to sound angry. I am passionately engaged in a
> spirited discussion! :-)
> --
> ___________________________________________________________
>
> Shawn Kendall Full Sail Real World Education
> Course Director 3300 University BLVD
> Real Time 3D for Gaming Winter Park FL 32792
> [EMAIL PROTECTED] http://www.fullsail.com
> ___________________________________________________________
>
> ===========================================================================
> 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".
===========================================================================
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".
