Magnit.NodeGraph VS nodezator

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.

I really wish Livecode hadn't pulled their opensource/Community Edition (and I'd be very glad for someone to do something with that code).

Gambas is something I keep wanting to try and seems promising.

I did one small app w/ Python and TKinter, but it was a dense wall of text/code when I was finished and not something I was interested in revisiting. I keep seeing suggestions that Python w/ QT support is supposed to be quite good.

One unlikely option is Google's Blockly (which I wish had a stand-alone desktop implementation which would make graphical programs), which has a nifty version implementing OpenSCAD:

https://www.blockscad3d.com/editor/

which I've used a fair bit. Moving on from there, there is: https://github.com/derkork/openscad-graph-editor which has the advantage of encompassing the entirety of OpenSCAD. It's also possible to wrap up Python using PythonSCAD.org

If you're willing to consider other node/line connection systems two promising options are:

https://ryven.org/

and

https://nodezator.com/

What sort of coding, on what sort of projects do you want to do?

The problem here is that a fundamental question has not been answered, and as far as I can tell, has not been addressed by any of these visual environments:

What does an algorithm look like?

Herman Hesse alluded to this in his novel _The Glass Bead Game_, but despite decades of discussion and work, no one has made a convincing pysical representation of that system.

I love the concept, and have made some moderately complex attempts, e.g.,:

https://www.blockscad3d.com/community/projects/1430644

https://github.com/WillAdams/gcodepreview

it always devolves to screen size being out-paced by problem complexity --- one gets something of an inkling of this at:

https://scriptsofanotherdimension.tumblr.com/

Alternately, one can just break a project down into modules, but then the top-level view becomes the wall of text representation (albeit w/ nice lines or captured into pretty boxes) which one is ostensibly trying to escape.

I'd love to see someone succeed in this, and I've been using:

https://github.com/derkork/openscad-graph-editor

quite a bit, and put a bit of money towards:

http://nodezator.com/

https://nodezator.com (app website, work in progress)

Some of the code (after being refactored/improved) and many of the lessons I gained from my experience developing this prototype can be seen in my most recent and more mature app, nodezator, which uses pygame as well.

I prefer this sort of programming system.

Mostly these days I do 3D modeling, so I'm using a Blockly version of OpenSCAD:

https://www.blockscad3d.com/editor/

but I'd really like to see a nice, stand-alone desktop development environment like to Scratch which isn't encumbered by a sandbox and which is able to write and append to local files and which is easily installed and which runs reliably.

Crashed and burned on pyFlow, Ryven, GraphSCAD, and a bunch of others.

Currently hoping that Nodezator (a node programming system based on pygame) will pan out --- it just needs branches and loops for my purposes:

http://nodezator.com

In the meanwhile, I'm copying OpenSCAD code out of BlockSCAD and pasting it into RapCAD:

https://forum.makerforums.info/t/g-code-preview-using-opensc...

Nodezator is out since last weekend! Install instructions on https://github.com/KennedyRichard/nodezator and manual on https://manual.nodezator.com Nodes from matplotlib demonstration available on https://github.com/KennedyRichard/matplotlib_example_node_pack Don't forget to install matplotlib as well to load the nodes properly.

I'd like to see one accepted and installed by default and easily used and nicely integrated --- perhaps some other tool should be tried --- I've been working w/ Nodezator: http://nodezator.com/ and it has the advantage of making quite straight-forward Python3 code.

Installations instructions and download on this github link.

If you have ideas/suggestions/concerns/constructive criticism you can share your thoughs on https://github.com/KennedyRichard/nodezator/discussions