Three days before this issue went live, my operating system had an argument with the beta version of a VRML browser that I had installed the night before. The browser won the argument and trashed many of my important configuration files. It took several hours to figure out what was wrong and restore my system.
At first I felt like using this forum as a bully pulpit to decry the evils of the company who made this software. But I subverted those base thoughts and, after I calmed down, I was able to learn some things:
1. Don't install software three days before a deadline. 2. The people who make this software need my help. They need to know what happened to me, a member of the community, so that they can fix it before it happens to someone less technical.
I say all this only to give a little perspective. The community as a whole is overworked right now. Content developers complain that the tools aren't keeping up with the spec. Spec experts are frustrated by the complexity and number of issues that remain unsolved. Tool developers are disappointed with the quality and quantity of input they get. And users are complaining that the community is too slow to implement the new spec.
Be that as it may, we are the makers of our own destiny. If this effort fails or succeeds, we will ultimately be responsible. Therefore it is our duty to take action. I am not saying that we all have to work harder. But if you don't feel overworked right now, you may want to consider putting in a few more hours.If you have a bug, don't complain to a colleague; report it. If you have a suggestion, make it known. If you have an idea for a VRML world, make it. It is the least you can do to ensure that VRML lives up to its potential.
John Gluck.
#VRML V2.0 utf8 | WorldInfo | ViewPoint | Shape .
NavigationInfo | Java Chat | Subscribe | Tell Friends© 1996 Aereal, Inc. Please send suggestions to suggest@vrmlsite.com