O3D: Difference between revisions
No edit summary |
|||
| Line 20: | Line 20: | ||
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 (programming)|AJAX]] and/or [[Comet (programming)|COMET]] in real-time. Traditional compilation of source code, application resources, and object libraries is no longer necessary, since all of these aspects are loaded in real-time. These remote resources may be designed, developed, and maintained outside the core rendering or view application within a typical object oriented [[Model–view–controller|MVC]] application. The direct result of this, explicitly makes development of rich 3D application easier, as you do not need to recompile your O3D application per resource changes. This allows for a more robust and distributive approach when designing 3D applications. |
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 (programming)|AJAX]] and/or [[Comet (programming)|COMET]] in real-time. Traditional compilation of source code, application resources, and object libraries is no longer necessary, since all of these aspects are loaded in real-time. These remote resources may be designed, developed, and maintained outside the core rendering or view application within a typical object oriented [[Model–view–controller|MVC]] application. The direct result of this, explicitly makes development of rich 3D application easier, as you do not need to recompile your O3D application per resource changes. This allows for a more robust and distributive approach when designing 3D applications. |
||
== See also == |
|||
[[WebGL]] - An open standard for showing hardware accelerated 3D graphics with [[JavaScript]] |
|||
== References == |
== References == |
||
Revision as of 22:47, 14 February 2010
| Repository | |
|---|---|
| Written in | JavaScript |
| Operating system | Cross-platform |
| Type | JavaScript API |
| License | BSD license |
| Website | http://code.google.com/apis/o3d/ |
O3D is an open source (BSD license) JavaScript API[1] 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, or massive online virtual worlds. O3D is currently in Google's incubation lab, and is deployed as an experimental web browser plugin.[2]
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 re-usability amongst application resources, while providing a robust interface to the client's CPU and GPU using JavaScript. Additionally, O3D uses a plug-in based architecture which allows 3rd party developers to integrate custom functionality such as pre and post render effects, particle systems, and or physics engines for example.
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 is no longer necessary, since all of these aspects are loaded in real-time. These remote resources may be designed, developed, and maintained outside the core rendering or view application within a typical object oriented MVC application. The direct result of this, explicitly makes development of rich 3D application easier, as you do not need to recompile your O3D application per resource changes. This allows for a more robust and distributive approach when designing 3D applications.
See also
WebGL - An open standard for showing hardware accelerated 3D graphics with JavaScript
References
- ^ O3D main developer's page from Google Code
- ^ O3D preview from Ars Technica
External links
- O3D Developers' Site
- GWT-O3D Developers' Site
- O3D Discussion Site
- Google 3D Warehouse (Online 3D Model Repository)
- Google Sketchup (3D Modeler)
- A set of tutorials on how to create an O3D application
 | This computing article is a stub. You can help Wikipedia by expanding it. |