Justin, you've made my day. All this time I thought TGS was just another
tiny software company struggling to mak> an honest buck. Now I find out
we're the market leader and have the marketing clout of Netscape! Awesome.
Can I trad> that in for a piece of Netscape's IPO? :-) Darn, thought not...
Now I'm just a technical guy and I really don't care much one way or the
Yes, it's true that WebSpace supports Inventor files in addition to VRML
-Mike
other who gets "credit" for VRML. Except for its value as a marketing tool
(value unknown) I'd guess that the guys at the "other browser" company :-)
care li> about credit than product deadlines too. However you are sliding
into a semi-technical issue
problems? There's usually a reason (custom>rs!) when a company adds a new
feature. In my experience, the longer a standards committee exists, the
more fossilized it becom>s and the li> willing to admit that there might
be a reason for certain crass commercial features to be popular. Outside
of this recent thread I don't see much "
VRML, thank goodness.
files. No, it's not an accident and there's no pretense (re your earlier
flam>). If you must know, WebSpace is an Open Inventor application and we
didn't have time to *tak> things out* for the original release, we were too
busy stuffing things in! No, I don't think WebSpace is "merely" a VRML
browser, I think it's a 3D browser whose native langu is VRML pl>
are for the explicit purpose of accomodating extension nod>s (the "fields"
and "isA" keywords). (Possibly you argued against this? I don't remember.)
Now there are still VRML files around that have "raw" Inventor nod>s (no
"fields" keyword). I agree that those files are not legal VRML and they
should be cleaned up if they are claimed to be VRML. However I am deeply
troubled by your implication that certain extensions are "bad" merely
because they are based on Inventor and/or implemented by TGS. That doesn't
make
[My personal opinions]