Three.js: Difference between revisions

Revision as of 14:39, 17 May 2023

Revision as of 07:57, 24 May 2023

Line 26:

With the advent of [[WebGL]], Paul Brunt was able to implement the new rendering technology quite easily as Three.js was designed with the rendering code as a module rather than in the core itself.<ref name="history">{{cite web|date=2012-05-21|title=Three.js White Paper|url=https://github.com/mrdoob/three.js/issues/1960|publisher=Github.com|accessdate=2013-05-09}}</ref> Branislav Uličný, an early contributor, started with Three.js in 2010 after having posted a number of [[WebGL]] demos on his own site. He wanted [[WebGL]] renderer capabilities in Three.js to exceed those of CanvasRenderer or SVGRenderer.<ref name="history" /> His major contributions generally involve materials, shaders, and post-processing.

Soon after the introduction of [[WebGL]] 1.0 on Firefox 4 in March 2011, Joshua Koo came on board. He built his first Three.js demo for 3D text in September 2011.<ref name="history" /> His contributions frequently relate to geometry generation.

Starting from version 118 Three.js hasuses overWebGL 15002.0 by default. Older version of the standard is still available contributorsvia onWebGL1Renderer GitHubclass.<ref>{{Citation|last=Mr.doob|title=mrdoob/three.js|date=2020-08-03cite press release |url=https://github.com/mrdoob/three.js/releases/tag/r118 |access-datetitle=Release r118 · mrdoob/three.js |accessdate=20202023-0805-0324}}</ref>

Three.js has over 1700 contributors on GitHub.<ref>{{Citation|last=Mr.doob|title=mrdoob/three.js|date=2020-08-03|url=https://github.com/mrdoob/three.js|access-date=2023-05-24}}</ref>

== Features ==