beeglebug / behave-flow Goto Github PK

in reality, this UI could be used with a graph which has custom nodes, so the spec file in the library will not cover them, we need to use the graphRegistry to generate the spec object (using writeNodeSpecsToJSON)

Need links to the demo from this GitHub repository. Also should explain what this library is.

This graph no longer makes any sense:

So it should be prevented from the UI.

This is similar to variables. Custom events are explicitly declared at the graph level. And then they are referenced by the graph nodes.

Example here:
https://github.com/bhouston/behave-graph/blob/main/src/graphs/core/events/CustomEvents.json

If there is more than one flow socket on import or output, we should display the names.

For example with For Loop here, the first flow output is "loopBody" which fires each time there is an iteration and then there is a second flow output "completed" flow socket that fires once the for loop is complete.

Right now usability is impairs because there are no labels, see here:

In UE Blueprints nodes with different purposes have different colours. We should likely support the same. I think you can not completely infer the purpose so instead we should just allow for nodes to either assign themselves colors or assign themselves roles which map onto colors.

drag from a socket to nowhere should trigger a create popup

It would be convenient to see how a node is implemented without having to open my text editor.

probably just needs a stoppropagation somewhere

at the moment they have fixed widths which is hard to use when entering longer strings/numbers

This would require this feature: bhouston/behave-graph#44

This way we can continually add nodes / remove node types based on context. This would require this feature: bhouston/behave-graph#43

there's no many nodes now the list is too long, need a type ahead auto complete thing

UE has a concept of auto casting, but i think for now only allow connections between matching types

can you provide behave-flow in javascript instead of typescript

I've added explicit support for creating typed variables with default values. Right now variables are discarded when loaded into behave-flow.

There are a number of examples here: https://github.com/bhouston/behave-graph/tree/main/src/graphs/core/variables

I recently added node labels to the node spec.

I've written a means of listening to the execution flow via GraphEvaluator.onNodeEvaluation. It fires off NodeEvaluationEvents which you can then use to highlight nodes in the graph.

I think that maybe this should be paired with a "step" advance function rather than execute to end or something like this? Like a step-debugger?

Usually when the menu is triggered, I try to type right away assuming the search text box has focus. It doesn't though. So then I have to do a second click. Would be nice to optimize this workflow by focusing the text box right away if the menu opens.