Jump to content

O3D: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5) (Whoop whoop pull up - 21816
 
(34 intermediate revisions by 33 users not shown)
Line 1: Line 1:
{{ Infobox Software
{{Infobox software
| name = O3D
| name = O3D
| logo =
| logo =
| screenshot = [[File:O3D Beach Demo.png|300px|O3D Beach Demo]]
| screenshot = O3D Beach Demo.png
| caption = A screenshot from the ''Beach Demo''<ref>{{YouTube|id = uofWfXOzX-g|title = O3D Beach Demo}}</ref> used by Google to demonstrate O3D's capabilities
| caption = A screenshot from the ''Beach Demo''<ref>{{YouTube|id = uofWfXOzX-g|title = O3D Beach Demo}}</ref> used by Google to demonstrate O3D's capabilities
| founder =
| developer =
| developer =
| status = Active
| latest release version =
| latest release version =
| latest release date = <!-- {{release date|YYYY|MM|DD}} -->
| latest release date = <!-- {{release date|YYYY|MM|DD}} -->
Line 13: Line 11:
| genre = [[JavaScript]] [[Application programming interface|API]]
| genre = [[JavaScript]] [[Application programming interface|API]]
| license = [[BSD license]]
| license = [[BSD license]]
| website = http://code.google.com/p/o3d/
| website = {{URL|https://code.google.com/p/o3d/}}
}}
}}
'''O3D''' is an [[open source]] ([[BSD license]]) [[JavaScript]] [[Application programming interface|API]]<ref>[http://code.google.com/apis/o3d/ O3D main developer's page] from [[Google Code]]</ref> 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 [[video game|games]], advertisements, [[3D model]] viewers, [[demoware|product demos]], simulations, engineering applications, control and monitoring systems, or massive online [[virtual world]]s. O3D is currently in Google's incubation lab, and is deployed as an experimental [[NPAPI|web browser plugin]].<ref>[http://arstechnica.com/software/news/2009/04/google-releases-3d-graphics-plugin-for-browsers.ars O3D preview] from Ars Technica</ref>
'''O3D''' is an [[open-source software|open-source]] ([[BSD license]]) [[JavaScript]] [[Application programming interface|API]]<ref name="GCProject">[https://code.google.com/p/o3d/ O3D Project Page] from Google Code</ref> 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 [[video game|games]], advertisements, [[3D model]] viewers, [[demoware|product demos]], simulations, engineering applications, control and monitoring systems, and massive online [[virtual world]]s. O3D is currently in Google's incubation lab, and was originally built as a [[NPAPI|web browser plugin]].<ref>[https://arstechnica.com/software/news/2009/04/google-releases-3d-graphics-plugin-for-browsers.ars O3D preview] from Ars Technica</ref><ref>[https://code.google.com/apis/o3d/ O3D Old Plugin Developer's Page] from [[Google Code]]</ref> Since 2010, O3D is a JavaScript library implemented on top of [[WebGL]].<ref name="GCProject" />


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 [[Central processing unit|CPU]] and [[Graphics processing unit|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. It is important to note that the plugin is written in C which communicates directly with the hardware, thus the speed of scene rendering is largely dependent on the graphics card of the computer rendering it.
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 [[Central processing unit|CPU]] and [[Graphics processing unit|GPU]] using JavaScript.


Originally, O3D used a plug-in based architecture which allowed 3rd party developers to integrate custom functionality, such as pre- and [[Video post-processing|post-render effects]], [[particle system]]s, and [[physics engine]]s. Because the plugin was written in [[C (programming language)|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 (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 [[3D modeling|models]] and their respective [[Texture mapping|textures]] dynamically, using [[Ajax (programming)|AJAX]] and/or [[Comet (programming)|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 programming|object-oriented]] [[Model–view–controller|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.<ref>http://blog.chromium.org/2010/05/future-of-o3d.html</ref>

⚫
On May 7, 2010, Google announced that O3D would be changing from a plugin to a JavaScript library running on top of WebGL.<ref>{{Cite web|url=https://blog.chromium.org/2010/05/future-of-o3d.html|title = The future of O3D}}</ref>


== See also ==
== See also ==
[[WebGL]] - An open standard for showing hardware accelerated 3D graphics with [[JavaScript]]
*[[WebGL]] - An open standard for showing hardware accelerated 3D graphics with [[JavaScript]]
[[VRML]] and [[X3D]] - Open standard from [[Web3D Consortium]]
*[[VRML]] and [[X3D]] - Open standard from [[Web3D Consortium]]
* [[List of WebGL frameworks]]


== References ==
== References ==
Line 31: Line 32:


== External links ==
== External links ==
* [http://code.google.com/p/o3d/ O3D Developers' Site]
* [https://code.google.com/p/o3d/ O3D Developers' Site]
* [http://code.google.com/p/gwt-o3d/ GWT-O3D Developers' Site]
* [https://code.google.com/p/gwt-o3d/ GWT-O3D Developers' Site]
* [http://code.google.com/apis/o3d/docs/groups.html O3D Discussion Site]
* [https://code.google.com/apis/o3d/docs/groups.html O3D Discussion Site] {{Webarchive|url=https://web.archive.org/web/20120310180553/https://code.google.com/apis/o3d/docs/groups.html |date=2012-03-10 }}
* [http://sketchup.google.com/3dwarehouse/ Google 3D Warehouse (Online 3D Model Repository)]
* [https://3dwarehouse.sketchup.com/ Trimble 3D Warehouse (Online 3D Model Repository)]
* [http://sketchup.google.com/ Google Sketchup (3D Modeler)]
* [http://www.sketchup.com/ Trimble SketchUp (3D Modeler)]
⚫
* [https://web.archive.org/web/20130508103227/http://www.jig3d.com/ A free 3D content importer/editor/publisher for creating O3D scenes]
* [http://www.sergemeunier.com/blog/o3d-tutorials/ A great set of tutorials on how to create an O3D application]
* [https://www.youtube.com/watch?v=RBFQHL-jPOo Google I/O 2009 - Developing On O3D: View From The Trenches YouTube video]
⚫
* [http://www.jig3d.com/ A free 3D content importer/editor/publisher for creating O3D scenes]
* [http://nakedsecurity.sophos.com/2013/04/16/researcher-30k-three-chrome-os-flaws/ Sophos Security: Researcher rewarded over $30,000 for finding 3 security flaws in O3D]


{{computing-stub}}


[[Category:Application programming interfaces]]
[[Category:Application programming interfaces]]
[[Category:Free 3D graphics software]]
[[Category:Free 3D graphics software]]
[[Category:Software using the BSD license]]

[[de:O3D]]
[[es:O3D]]
[[ru:O3D]]
[[uk:O3D]]

Latest revision as of 22:00, 18 November 2024

O3D
Repository
Written inJavaScript
Operating systemCross-platform
TypeJavaScript API
LicenseBSD license
Websitecode.google.com/p/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 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]

See also

[edit]

References

[edit]
  1. ^ O3D Beach Demo on YouTube
  2. ^ a b O3D Project Page from Google Code
  3. ^ O3D preview from Ars Technica
  4. ^ O3D Old Plugin Developer's Page from Google Code
  5. ^ "The future of O3D".
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=O3D&oldid=1258237359"