The capability bits that control access to the member variables of the Appearance class are: A live scenegraph is one that has either been compiled or has been rendered. That is, the application developer must specify which Appearance member variables will be modified after the Appearance is attached to a live scenegraph. The Appearance class controls access to its member variables through the familiar, but rigorous, process of setting capability bits. The Appearance class itself does not define any of the properties that control Shape3D appearance, but instead packages Appearance subcomponents, such as PolygonAttributes, RenderingAttributes, and so on. A Shape3D object basically contains Geometry and Appearance. The Appearance class contains member variables that together define an appearance state for a Shape3D object.
#JAVA 3D ARRAY EXAMPLE CODE#
I encourage you to examine the code for the example and run it as you work through this chapter-most of the sections will be significantly clarified by this interactive example.įigure 9.1 The AppearanceTest example application allows Appearance settings to be modified at runtime 9.2 Appearance
One of the lengthier examples of the book accompanies this chapter: AppearanceTest (illustrated in figure 9.1) allows you to dynamically modify most of the Appearance attributes on a simple scene. The tables include references to OpenGL functions where appropriate and useful. I have prefaced each section with a table listing the capability bits that control access to the specific feature being discussed. Consult the detailed Sun API reference for a method-by-method summary of the classes. Emphasis is placed on areas of potential confusion or typical problems. What follows is an overview of the NodeComponent-derived classes that define a Java 3D rendering state for a Shape3D object. It is useful to think of the Java 3D renderer traversing through the defined scenegraph when it encounters TransformGroups, it applies matrix transformations when it encounters a Shape3D Node, it applies the Shape3D’s Appearance state-all before executing the Shape3D object to generate native graphics API calls. The Appearance object defines rendering state information that must be applied to the rendering pipeline before the raw geometry within the Shape3D is rendered. Compared with learning the plethora of separate OpenGL methods to specify appearance, the OO nature of the Java 3D design pays dividends.Īn instance of an Appearance object is associated with each Shape3D geometric object in the scenegraph. This is one of the best-designed areas of Java 3D with a little experience you can quickly learn to navigate the various classes that, when combined, specify object appearance. For example, an Appearance has a Material class, a PolygonAttributes class, a RenderingAttributes class, and so on. Java 3D defines “has-a” relationships between the classes that control overall rendering appearance. Java 3D contains a host of classes to specify the rendering attributes for geometric primitives, such as color, texture, back-face removal, and so on. After reading this chapter, you should be able to dynamically modify the appearance of the geometry within your scenegraph. The Java 3D Appearance class enables you to set rendering attributes for the geometric primitives in your scene-at startup, during scenegraph creation, or dynamically at runtime. Java 3D Programming.Chapter 9 CHAPTER 9 Setting geometry appearances
0 kommentar(er)
