Denis Chan wrote:
-How can we compare X3D and Java 3D, in terms of functionality.
Simple - one is a programming API, the other is a file format. With a
programming API, the potential approaches to solving a problem are
limitless, with a file format, you are bound by the rules and
conventions of the specification.
-And the Pros and cons for supporting Wed 3D applications.
That is highly dependent on your application. What is your application
trying to do? That will determine whether you want to support one or
more of the file formats defined by the Web3D consortium, or any other
file format for that matter.
--
Justin Couch http://www.vlc.com.au/~justin/
Java Architect & Bit Twiddler http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"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".
