|
Xj3D VRML/X3D Code API | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Class Summary | |
| BrowserNavigationToolbar | A toolbar for all navigation commands. |
| VRMLBrowserAWTPanel | A brower that uses the AWT panel and labels to draw render the UI with. |
| VRMLBrowserJPanel | Swing JPanel implementation that wraps the functionality of a VRML browser into a convenient, easy to use form. |
| VRMLOGLBrowserFactoryImpl | An implementation of the EAI BrowserFactoryImpl interface
that creates a browser that uses OpenGL for the renderer. |
| X3DBrowserAWTPanel | A brower that uses the AWT panel and labels to draw render the UI with. |
| X3DBrowserJPanel | A swing panel that implements a single view browser using Java3D as the X3D renderer. |
| X3DNRBrowserFactoryImpl | Factory implementation for X3D SAI which will produce components using the Null renderer. |
| X3DOGLBrowserFactoryImpl | Factory implementation for X3D SAI which will produce components using the OpenGL renderer. |
Classes that are used to create or be a full browser panel embedded within an application.
The majority of these classes are used to support the EAI/SAI functionality so that a user can create and manipulate a full VRML/X3D browser as part of an application. The intention is that the programmer will never need to deal with all the other classes provided by Xj3D and just stick with the standards compliant EAI or SAI interface.
Creating a component using either of these interfaces starts with
registering the appropriate factory implementation with the EAI/SAI.
An end user should never have to do this, however as both standards
define a way for each browser to nominate itself as the implementation
of choice, through the use of Java properties files. To make sure you
are using the right implementation, look for either vrml97.properties
or x3d.properties in your CLASSPATH. Check that the entry is pointing
to the appropriate class from this package. After that, all you need
to do to use the SAI or EAI is to call the appropriate create method
from the factory API. If you find yourself needing to call the
setBrowserFactoryImpl() method then you are doing something
wrong as this now restricts the code to a particular SAI/EAI implementation.
This is wrong, and creates non-portable code.
These particular files are specific to the Aviatrix3D OpenGL based renderer.
|
Xj3D VRML/X3D Code API | ||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||