NOTE: Precedents
NOTE: 0002 — Wednesday 29th November 2017
As part of the process, 7 hours will be dedicated to research and application.
WEEK 0001: Thursday 23rd November 2017
Hours: 8 (9AM — 5PM)
The first day was spent in brainstorming possible workarounds on achieving a workflow / application that would allow for allow for visual scripting applications in architecture be accessible on the web.
More specifically, a platform for collaboration. Instead of modelling, we replace that method with the process of programming logic to a building.
There were a number of things I stumbled upon during this research process:
Title: Collaborative Code Editor for Developing at an Urban Scale
- Three.js
- Python
- Code Editor
- Open-source components
Examples:
- three.py — “Utilities for integrating Python with three.js.”
- Pythreejs
- “A Python / ThreeJS bridge utilizing the Jupyter widget infrastructure.”
- Requires the installation of python and pip
- The python arrangement is note closely compatible with Python for Rhinoceros
There would be two parts of the workflow that could potentially assist in creating this one large project:
- Python to Three.js
- Processing Python using JavaScript
- Processing Python script to Three.js Geometry - Web-based Code Editor
- Storying, accessing and editing from a repository (Github)
- Live?
The resulting research into these options looks like it may be easier to create Rhinoceros as a server, which is then piped through to the web application.
© Emily Y Leung and Project Avalanche, 2017. Unauthorized use and/or duplication of this material without express and written permission from this site’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Emily Y Leung and Project Avalanche with appropriate and specific direction to the original content.
Last modified on Thursday 30th November 2017
