In the first stage of the VRML browser wars, this kind of coolness was king. As we enter the second stage, simplicity and reliability are the top crowning factors a VRML browser must have.

Whatever happens, don't let the browser crash! When in "player" mode, never show an error message. The great thing about HTML was that you anybody could write something resembling HTML and the browser would never complain, something would show up (with the exception of horrid tables!! argh!). If you want to put debug features in your browser, that's great, but make it a mode that someone has to switch into.

Also, color palettes! a word about color palettes!

I got my father a copy of Civilization II for his birthday. Guess what it does when it wants to display two windows of color-intensive applications! It converts the inactive window in grayscale, while the active window appears in full peachy color. Maybe browser writers (Netscape? Microsoft?) could learn something from this.

There are so many useful ways of integrating HTML and VRML, but people will be reluctant to do so if the color palettes go all wacko.

In closing, here's a reminder of simple things that will alienate the general browser-using public.

• browsers crashing
• color palettes going wacko
• links not working (because your browsers's sucking up all system resources)

The HTML browser writers had it all easier, since there was just a small audience of browser users when they started out. Now it's time for VRML browsers to start maturing, even as they are rewritten for VRML 2.0.

Adrian Scott
adrian@aereal.com
Publisher
VRMLSite Magazine