Three.js: Difference between revisions

Revision as of 15:40, 19 March 2021

Revision as of 10:44, 2 April 2021

Line 30:

Three.js was first released by Ricardo Cabello to GitHub in April 2010.<ref name="firstcommit" /> The origins of the library can be traced back to his involvement with the [[demoscene]] in the early 2000s.<ref>{{cite web|url=https://www.youtube.com/watch?v=LXWYOF4VibE|author=NVScene|publisher=YouTube|title=NVScene 2015 Session: Reinventing The Wheel - One Last Time (Ricardo Cabello)}}</ref> The code was first developed in [[ActionScript]] and ported to JavaScript in 2009. In Cabello's mind, the two strong points for the transfer to JavaScript were not having to compile the code before each run and platform independence. With the advent of [[WebGL]], Paul Brunt was able to add the renderer for this 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|url=https://github.com/mrdoob/three.js/issues/1960 |title=Three.js White Paper |publisher=Github.com |date=2012-05-21 |accessdate=2013-05-09}}</ref> Cabello's contributions include API design, CanvasRenderer, SVGRenderer, and being responsible for merging the commits by the various contributors into the project.

Branislav UlicnyUlič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.