Haven’t had the opportunity to try it yet, but this looks fantastic. Soo glad I didn’t embark on building a similar tool.
What’s really exciting to see is execution stacks of nodes (with shared variable capabilities and inheritance). IMO this is a vast improvement over just a loose node graph when it comes to representing a sequential build process.
A few questions:
-
Can you visualize the progress of the stack/graphs during the execution?
-
Can you visualize and/or report when a node fails? And as a follow-up question, can you save and pull up a prior build attempt state (for troubleshooting)?
-
Are there performance implications with the token system? I would probably keep Python code extremely lite in nodes anyways, only referencing single function calls from core scripts.
-
Do NXT’s graph files follow a common format like JSON?
-
Can you save/reference/inherit individual nodes or node stacks?
-
Is it possible to execute a graph without the full interface, and expose variables that could be modified from an execution command?
-
If you can expose variables to be modifiable by a run command, is it possible to also query what they are. (Think building a dynamic property panel from the graph)
Sorry I have soo many questions! Really just speaks to my level of interest.