# NodeMaterial visual editor?

**URL:** <https://discourse.threejs.org/t/nodematerial-visual-editor/12479>\
**Category:** Questions\
**Tags:** node-material\
**Created:** [February 3, 2020, 5:08am UTC](https://discourse.threejs.org/t/nodematerial-visual-editor/12479 "2020-02-03T05:08:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pailhead](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/pailhead/32/85_2.png) [@pailhead](https://discourse.threejs.org/u/pailhead)\
**Post date:** [February 3, 2020, 6:59pm UTC](https://discourse.threejs.org/t/nodematerial-visual-editor/12479/3 "2020-02-03T18:59:02Z")

</div>

Want to throw my experiment into the mix:

> [@Visual shader editor wip](https://discourse.threejs.org/t/visual-shader-editor-wip/11129):
>
> link -\> [http://dusanbosnjak.com/test/nodes/](http://dusanbosnjak.com/test/nodes/) I’ve been working on a node editor and i’ve cooked up a version that generate’s three’s ShaderMaterials. It’s super WIP and clunky, but i think it’s more or less complete as in that it can persist whatever’s being created, display the result using three, and spit out a JS class into the clipboard (export) although that bit is most likely broken. This is my pet project that i’m using to experiment with various web technologies. I had it hook…

I really want to check these others out, i’ve started mine twice from scratch and still thing the architecture is horrible. Sort of happy with the performance, but not the convenience. The approach though, should be able to generate materials, possibly for all three.js versions so far if the hooks are added to the GLSL from each.

---

_[View the full topic](https://discourse.threejs.org/t/nodematerial-visual-editor/12479)._