O3D

O3D is an open-source (BSD license) JavaScript API[2] created by Google for creating interactive 3D graphics applications that run in a web browser window or in a XUL desktop application. O3D may be crafted for use in any application area; however, it is geared towards games, advertisements, 3D model viewers, product demos, simulations, engineering applications, control and monitoring systems, and massive online virtual worlds. O3D is currently in Google's incubation lab, and was originally built as a web browser plugin.[3][4] Since 2010, O3D is a JavaScript library implemented on top of WebGL.[2]

O3D

A screenshot from the Beach Demo[1] used by Google to demonstrate O3D's capabilities
Repository	src.chromium.org/viewvc/chrome/trunk/o3d/
Written in	JavaScript
Operating system	Cross-platform
Type	JavaScript API
License	BSD license
Website	code.google.com/p/o3d/

O3D is viewed as bridging the gap between desktop-based 3D accelerated graphics applications and HTML-based web browsers. Proponents assert that creating a full-featured 3D graphics engine that can be downloaded and run through web browsers may eliminate the need to install large applications on a local desktop computer. This allows O3D to maximize reusability amongst application resources, while providing a robust interface to the client's CPU and GPU using JavaScript.

Originally, O3D used a plug-in based architecture which allowed 3rd party developers to integrate custom functionality, such as pre- and post-render effects, particle systems, and physics engines. Because the plugin was written in C, it communicated directly with hardware; thus, the speed of scene rendering was largely dependent on the GPU of the computer rendering it. Now, much of this same functionality is built into WebGL.

The main advantage O3D has over alternative desktop or console based 3D rendering engines is that O3D may load, render, and transform models and their respective textures dynamically, using AJAX and/or COMET in real time. Traditional compilation of source code, application resources, and object libraries are no longer necessary, since all of these are loaded in real time. These remote resources may be designed, developed, and maintained outside the core rendering or viewing application within a typical object-oriented MVC application. This makes developing rich 3D application easier because they do not need to be recompiled per resource changes, allowing for a more robust and distributive approach when designing 3D applications.

On May 7, 2010, Google announced that O3D would be changing from a plugin to a JavaScript library running on top of WebGL.[5]