nodes-io VS Magnit.NodeGraph

Yeah as another comment said, a 3D designer could make this render in Blender, then send you a video recording or multiple videos rendered to different dimensions that you can conditionally fetch on your site depending on the user's viewport width, but as the creator of this animation said in the IG comments, their project in particular was created with nodes. PixiJS is another great WebGL library, as is Three.js.

Some of the tools listed here look like this one: https://nodes.io

"Window" is a generative piece exploring the different densities formed by both rigorous and pseudo-random patterns through wobbly quadrilaterals. It lives as an NFT on the Tezos blockchain through the fxhash platform: you can mint a Generative Token with every iteration producing a unique piece based on a random hash. Here, the hash seed will determine the palettes, dithering, number of subdivisions and control the patterns. It is build on top of the Canvas API with the visual programming tool I am developing at Variable: Nodes.

Download Nodes.io from https://nodes.io/

There should be a tool that works like this: you can create nodes (like in nodes.io, Blender, many other graphics tools etc.), then add as many inputs and outputs as you want. The outputs work like spreadsheet cells: so you can add a formula from the inputs; you can also have "internal" cells in the node for intermediate calculations. In other words, each node is a tiny spreadsheet. You can save them as templates, group nodes together into bigger templates etc. There's a lot of design/planning in a lot of different domains that would benefit from a tool like this. Why doesn't it exist?

nodes.io says there are 9864 btc nodes

If you want to try it out yourself, try tools like https://nodes.io/ or the classic https://www.shadertoy.com/

- https://nodes.io/ seems to be closest to what you're looking for, and certainly looks the most polished. Their visual scripting / node editor is pretty good, but I don't know how it integrates with / overlaps onto three.js

Nodes.io – A new way to create with code\ (68 comments)

Oh sweet! I was in the middle of building my own version of a node-graph component (ref: https://github.com/catapart/Magnit.NodeGraph), but the `canvas.js` implementation from this JsonCanvas repo is exactly what I was trying to build. I really, really like how elegantly uncomplex it is. Could not have been more exactly what I was looking for. So thanks for this!

As far as the spec, I don't really like the idea of forcing well-known types for the nodes. A generic spec should allow for entirely generic nodes that can represent themselves to consuming functions with a 'type' property as a key, as well as arbitrary data types linked to arbitrary nodes. For instance: one of my use cases is an 'addition' node, which would take two number values and produce a number value. This node would also use an entrance execution pin as well as an exit execution pin.

If the spec were to include a 'pin' data type and capture the type keys and labels for pins, those pins could be stored as a list on the node. Then, the type property could just tell the executing context how to route the node data and the pin properties would bring type safety to the functional inputs passed to the mapped function.

Anyway, I assume all of that is out of scope for initial offerings, but that's my two cents on a generalized node spec. Regardless, thanks again for the sweet, simplistic node graph implementation!

> If people don't intrinsically understand you, maybe you need to go in to more detail so your explanation isn't so abstract.

People did; you didn't.

> Ergo, vis-a-vi have you ever actually tried making a graph that is rearranging itself while you're using it?

No one said anything about "while you're using it". Linters don't fuck up your text as you type it. It's a utility like anything else. And, YES, I have built a working version of one. It doesn't use machine learning/tensors at all, and it's a fucking nightmare to develop. I can see exactly where those things would help me. It's too abstract, to you, to understand? That's a shame! But other people seem to get it, so if you are having trouble, maybe try approaching your ignorance with openness and curiosity instead of cynicism and trivialization ('uncross some lines').

If you want to know how much time I've spent working on node edge graphs, you wouldn't believe me. But I can at least point you to the start of the web-component version I'm porting: https://github.com/catapart/Magnit.NodeGraph

Shameless plug time! I've been working on something like this as a custom web component with no dependencies: https://github.com/catapart/Magnit.NodeGraph

Not the most feature rich - I'm developing it for a single project, so that's project's needs come first. But it's rudimentary enough to start from if you're looking to build your own, and it's simple enough to customize if it already does what you need.