Lesson 76 - Interactivity in Shout3D - Part 1

Lesson 76 - Interactivity in Shout3D - Part 1

This soon-to-be-released package allows developers to embed a realtime, interactive 3D rendering engine directly into a Web page, without the need for plug-ins on the client's computer. If you haven't already seen this marvel in action, take a look at Les

So Shout3D is an expression of a larger movement, and stands firmly on the VRML tradition. I'm also convinced that eliminating the need for a plug-in application is critical to the success of 3D on the Web, and Shout3D has clearly solved this vexing problem.

But perhaps more important than all these factors is the way Shout3D Models handles interactivity. Realtime 3D on the Web can only make sense as a highly interactive tool that invites user participation and makes the use of the Internet easier and more enjoyable. Interactivity is the central issue for Web 3D, far more important than the underlying graphics. The tools for creating such interactivity must be powerful and flexible. Shout3D 1.0 uses Java, a full-strength programming language as the vehicle for interactivity. From what I can see, there is little or nothing that cannot be achieved using Shout3D's Java class library.

In this lesson, I'd like to introduce you, in a general way, to how interactivity is achieved in Shout 3D Models. Ultimately, this is an issue of writing the specific Java code (or using the excellent code examples that are provided with the package). But beyond the coding are broader issues that must first be addressed. For example, what does "interactivity" really mean here?

Interactivity implies responses by the application to user input. The responses might be starting an animation, rotating an object in the scene, zooming the camera, changing the lighting, making an object transparent, or loading a new scene. In fact, this list doesn't even scratch the surface of the possibilities. The user input is in the form of actions taken with the mouse or the keyboard. The application (or rather, the Java applet, in the specific case of Shout3D) must receive user input and respond with changes in the 3D scene.

This definition of interactivity is simple enough, and common to almost every program you are currently familiar with. But special considerations apply in the case of realtime 3D Modelsrendering. A realtime 3D renderer, such as a VRML player or the Shout3DApplet, renders frames as fast as it can. As soon as a frame is rendered, the renderer is asked to render the scene again, creating a rendering loop. Thus your frame rate depends on your microprocessor and the demands being made on it, and thus it cannot be fixed in advance.

son 75 right now.

POST COMMENT

Stem Cell: A Revolution in THE Modern Biology The Advantage of Invisible Braces from Invisalign 3 Different Types Of Modern Yoga Poses The Poconos Why people are looking into nursery gliders Signs Your Little one Might Be Autistic Watch The Amazing Race Season 18 Episode 2 - I Never Looked So Foolish in My Whole Entire Life Heroes Episodes (A Journey By means of Time) How to Increase Traffic Like Never Before! Cuba releated stuff Making Museums: One Hospital At a Time Looking for Your Souls within Rift The latest Trend in Tv Viewing