unit
behave-graph
unit | behave-graph | |
---|---|---|
12 | 4 | |
2,505 | 284 | |
- | - | |
9.7 | 7.7 | |
9 days ago | 5 months ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unit
- Unit – Next Generation Visual Programming System
-
Visual Node Graph with ImGui
https://github.com/samuelmtimbo/unit recently, which at least uses some kind of hinted auto-layout (besides the more propriety fancy)
I really want to see more graphical coding for years, but node/graph-based and blockly seem to be the only approaches that got sone traction so far. So I like this thread and it seems at the right place.
I'd wish to see
- Next Generation Visual Programming System
-
Unit (Visual Programming System) [video]
Interesting, and clearly a lot of work's gone into this (60,000 lines of Typescript), particularly the UI, which is impressive (if, sometimes, over the top). I've been developing a similar system (http://www.fmjlang.co.uk/fmj/tutorials/TOC.html) and it's interesting to note the similarities and differences.
Similarities: code as directed graphs (less obvious in FMJ); can only connect outputs to units of compatible type; if and wait (looping is handled differently); sticky values; sliders. These design decisions are practically forced on you, but are often absent in earlier visual dataflow languages (e.g. Prograph, LabVIEW).
Differences: (1) inputs are named in Unit, ordered in FMJ (though they're named in formulas and edges can be labelled). (2) I experimented with automatic code layout but found this was too slow and not always what I wanted. Well done for getting this to work. (3) FMJ is now fully homoiconic - this maybe isn't a priority for Unit.
The Unit design philosophy is explained in https://github.com/samuelmtimbo/unit/blob/main/src/docs/conc... . This doesn't mention earlier approaches (e.g. the Manchester Dataflow Computer, Prograph) and it seems to be based on vaguely similar ideas developed more recently (Morrison's Flow Based programming; possibly React and similar systems for web development - I'm unfamiliar with these).
I have a number of questions:
(1) How does the type system work? Is it Dependently typed, Hindley-Milner, or something more basic? (FMJ is Hindley-Milner, with dependent typing partially implemented). How are new types be defined?
(2) How is the visual representation stored? One criticism I faced was that people wanted a readable textual representation which would work well with existing version control systems, a problem I have now largely solved.
(3) How are runtime errors handled?
(4) Is recursion supported? (I assume yes, but I didn't see any examples.) What about macros?
(5) What does Unit compile to? (FMJ has an experimental compiler where programs are compiled by running their source without evaluating their inputs, output is Lisp.)
- Unit.land
-
A personal history of visual programming environments (2021)
I enjoyed reading this. I knew of quartz composer but I never did anything with it.
I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural).
Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more research around flow based programming for infrastructure management.
I plan to get this sort of info published on my website which I have neglected for half a decade or more but if you are interested in visual programming you might enjoy checking these out:
Unit from Samuel Timbó:
https://github.com/samuelmtimbo/unit
https://ioun.it/
A video of me exploring what I figured out about it (while also learning to stream) https://www.youtube.com/watch?v=vwknTfGVDq8
Behave-Graph from Ben Houston:
https://github.com/bhouston/behave-graph
And the products I learned so long ago
[0] Houdini https://www.sidefx.com/products/houdini/
[1] Fusion https://www.blackmagicdesign.com/products/fusion
-
Ask HN: More “experimental“ UIs for editing/writing code?
https://github.com/samuelmtimbo/unit
- A code drawn in unit is simply a Directed Graph.
- Programming can be partially performed by Gesture and by Voice.
- Unit: Next Generation Visual Programming Platform
behave-graph
-
Show HN: NPM package for a visual scripting editor
How does this compare to the open source behave-graph library?
https://github.com/bhouston/behave-graph
Is Luna based on behave-graph?
-
A personal history of visual programming environments (2021)
I enjoyed reading this. I knew of quartz composer but I never did anything with it.
I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural).
Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more research around flow based programming for infrastructure management.
I plan to get this sort of info published on my website which I have neglected for half a decade or more but if you are interested in visual programming you might enjoy checking these out:
Unit from Samuel Timbó:
https://github.com/samuelmtimbo/unit
https://ioun.it/
A video of me exploring what I figured out about it (while also learning to stream) https://www.youtube.com/watch?v=vwknTfGVDq8
Behave-Graph from Ben Houston:
https://github.com/bhouston/behave-graph
And the products I learned so long ago
[0] Houdini https://www.sidefx.com/products/houdini/
[1] Fusion https://www.blackmagicdesign.com/products/fusion
-
Clara.io Shutting Down
Fun fact, a lot of it is open source, just not where you would expect it. During the creation of Clara.io I created over 200 PRs to Three.js:
https://github.com/mrdoob/three.js/pulls?q=is%3Apr+author%3A...
The problem with open sourcing it wholesale at this point is a challenge because parts of the tech stack became parts of Threekit.com. Threekit.com is VC funded and an ongoing business operation.
I do what I can with open source still, see:
https://github.com/bhouston/behave-graph
https://github.com/threeify/threeify
-
Node-Based UIs
Don't forget behave-graph/behave-flow, the Unreal Engine Blueprints / Unity Visual Script like interaction/behavior system:
https://github.com/bhouston/behave-graph
What are some alternatives?
vue-flow - A highly customizable Flowchart component for Vue 3. Features seamless zoom & pan 🔎, additional components like a Minimap 🗺 and utilities to interact with state and graph.
litegraph.js - A graph node engine and editor written in Javascript similar to PD or UDK Blueprints, comes with its own editor in HTML5 Canvas2D. The engine can run client side or server side using Node. It allows to export graphs as JSONs to be included in applications independently.
lisperanto - Lisperanto is a spatial canvas for programming; Lisperanto is a spatial canvas for knowledge; Lisperanto is a spatial canvas for ideas;
nodes-io - A new way to create with code.
impulse - Impossible Dev Tools for React and Tailwind
threeify - A Typescript 3D library loosely based on three.js
metadesk
demo
newspeak - Newspeak is a live object-capability language in the Smalltalk tradition
GoJS, a JavaScript Library for HTML Diagrams - JavaScript diagramming library for interactive flowcharts, org charts, design tools, planning tools, visual languages.
nodezator - A multi-purpose visual node editor for the Python programming language
t3 - Tooll 3 is an open source software to create realtime motion graphics.