[X3D-Public] O3D - Google's 3D JavaScript API

[Len Bullard]

"If there's something  lacking in VRML/X3D such that they  
can't support Google Earth and Sketchup in the browsers, then these  
items should be addressed with Google."

Maybe X3D isn't the problem.  Help on standards is appreciated but so far
the X3D vendors don't need Google's help to write the best X3D browsers.
Holger, Tony, Sergey and the rest know more about that than Google does.

It's true.  They have the experience and the chops that the Google team
doesn't.  Open source, transparency, all the good stuff, don't mean anything
against real chops.

It can't be the case that after almost a decade and a half of continuous use
on the web that people are trying to make the case that VRML and X3D don't
work.  Hell, they are the only things that have continuously worked and the
web owns them instead of the other way around.

Again: what about O3D is a better scene graph?

Sorry, this time the shoe is on Google's foot.  X3D has nothing to prove.

len


From: x3d-public-bounces at web3d.org [mailto:x3d-public-bounces at web3d.org] On
Behalf Of John Carlson


I think that Google is trying to spread its JavaScript V8 engine into  
everyone's browser.  Perhaps X3D vendors should pay attention and get  
a faster JavaScript implementation, to compete.  I think that Google  
has interest in getting a fast Google Earth and Sketchup into all  
browsers.  If there's something  lacking in VRML/X3D such that they  
can't support Google Earth and Sketchup in the browsers, then these  
items should be addressed with Google.

John