Best Practices Tutorial

Index
chapter 1 | chapter 2 | chapter 3
chapter 4 | chapter 5
chapter 6 | chapter 7

home | developer central

Chapter 7- Web Driver API Particulars

previous chapter | index

For our final chapter, we'll look at specific areas of the Web Driver API that deserve some caution. These areas include:

Lights

As mentioned in the previous chapter, having lots of lights can be expensive- you should use only as many lights as you need, and set the light ranges to an appropriate distance.

Collision detection

The collision engine in the Web Driver saves you as a 3d application developer from one of the most difficult aspects of 3d programming; but, if used improperly, you can inadvertently bog your app down by using collision checks that you don't need. Some ways to improve collision efficiency include:

Actors

Actors give you access to the latest features of the Web Driver, such as mesh deformation, LOD optimization, and material effects. But, as with all flashy features, they are also resource-intensive, and are a point to watch when creating an efficient application.

Other objects

Some other particulars of the Web Driver API that you can use to economize your application include:

Conclusion

This tutorial has covered a lot of ground, and has gone over both general and specific ways you can write a better Web Driver application. There have been a lot of warnings about what's expensive in Java and the Web Driver API here; the intention was not to tell you not to use these features, but to give you an idea of how to use them more efficiently, so as to write an application that's not too slow or unstable, but still be able to take advantage of the best features that Java and the Web Driver have to offer.

 


previous chapter | index

2000 WildTangent Inc. All Rights Reserved. Website Terms & Privacy Statement