Wednesday, January 15, 2003 05:04 AM
There are a couple problems:
- You would have to know what OS the client has. The java3D API's rely heavily on the underlying OS Graphics engine -- either DirectX or OpenGL to run and they are specifically designed for that.
- You would have to place ALL the required classes in the jar file for that Applet or load a separate jar file with your applet onto the client computer. Which is a pain and takes a Loooonnnnggggg time.
The best thing is to require that the client loads the Java3D classes for his computer BEFORE you load your Applet. You can catch the "Class Not Found" exception when you try and access your firest Java3D API and request the client to install it.
The java3D APIs are cool, AND are portable IF the underlying 3D jars are loaded on the client machine.