<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[PROJECT AVALANCHE - Medium]]></title>
        <description><![CDATA[Documenting explorations in the fields of Architecture and Computer Programming - Medium]]></description>
        <link>https://medium.com/projectavalanche?source=rss----c3613254dd2a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>PROJECT AVALANCHE - Medium</title>
            <link>https://medium.com/projectavalanche?source=rss----c3613254dd2a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:59:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/projectavalanche" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NOTE: Precedents]]></title>
            <link>https://medium.com/projectavalanche/0002-precedents-be69374f2063?source=rss----c3613254dd2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/be69374f2063</guid>
            <category><![CDATA[computational-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[emily leung]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 01:16:46 GMT</pubDate>
            <atom:updated>2018-03-21T03:19:01.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0to9G5S5jIHjZc5xmVJLXA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/1qkyck-UL3g?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">James Pond</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>NOTE: 0002 — Wednesday 29th November 2017</p><p>As part of the process, 7 hours will be dedicated to research and application.</p><h3>WEEK 0001: Thursday 23rd November 2017</h3><p>Hours: 8 (9AM — 5PM)</p><p>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.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-usnbZ7FIw-6EzYyYkJew.jpeg" /></figure><p>More specifically, a platform for collaboration. Instead of modelling, we replace that method with the process of programming logic to a building.</p><p>There were a number of things I stumbled upon during this research process:</p><p>Title: Collaborative Code Editor for Developing at an Urban Scale</p><ul><li>Three.js</li><li>Python</li><li>Code Editor</li><li>Open-source components</li></ul><p>Examples:</p><ul><li><a href="https://github.com/jzitelli/three.py"><strong>three.py</strong></a> — “Utilities for integrating Python with three.js.”</li><li><a href="https://github.com/jovyan/pythreejs"><strong>Pythreejs</strong></a><br>- “A Python / ThreeJS bridge utilizing the Jupyter widget infrastructure.”<br>- Requires the installation of <a href="https://github.com/BurntSushi/nfldb/wiki/Python-&amp;-pip-Windows-installation">python and pip</a><br>- The python arrangement is note closely compatible with Python for Rhinoceros</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*cBGd4txEUH2rmYXr8jlWXg.gif" /></figure><p>There would be two parts of the workflow that could potentially assist in creating this one large project:</p><ol><li>Python to Three.js<br>- Processing Python using JavaScript<br>- Processing Python script to Three.js Geometry</li><li>Web-based Code Editor<br>- Storying, accessing and editing from a repository (Github)<br>- Live?</li></ol><p>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.</p><blockquote>© 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.</blockquote><p>Last modified on Thursday 30th November 2017</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be69374f2063" width="1" height="1" alt=""><hr><p><a href="https://medium.com/projectavalanche/0002-precedents-be69374f2063">NOTE: Precedents</a> was originally published in <a href="https://medium.com/projectavalanche">PROJECT AVALANCHE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>