week two – thursday 1st august
lecture notes:
Three.js is an archive of coding outcomes that are created in Java. It is modelled on the idea of learning through experimentation and building on what others have created.
The right hand menu has sliders and drop down menus that can alter the product/objects materiality, size or colour as well as environmental factors. These changes are reflected in the code that sits onto of the object. Seeing these changes occur in code and in the product itself helps you learn through seeing the changes without having to know the code.
As an experimental project, the three.js playground isn’t maintained so there are some elements which don’t always work.
z = depth
shape = mesh (is made up of material & geometry)
saving to the archive:
The three.js archive is not monitored and has thousands of outputs and forks saved in a list. The best way to ensure that our work is saved and viewable regardless of the changes within three.js. To do this you need to copy all of your code (ensuring you get all of the code) into a text editor such as Brackets. If you have any ‘if’ statements these need to be modified/deleted. Save the brackets file as an html and once it is saved it should be openable through your default web browser (chrome, safari etc.)
screenshots & outputs from three.js that I created before I learnt how to save them as working html files
Coding for Creative Practice 