Edges
An edge connects two nodes, or a node with a field of another node. Draw it by dragging from the connector of the selected node to the target.
Kinds
| Kind | When |
|---|---|
| straight | simple links |
| orthogonal | diagrams that route around nodes; the route can be drawn by hand |
| curve | mind maps and free-form diagrams |
| dimension | a distance label on drawings |
The role of an edge is separate from its kind: data, exec and reference. A data edge carries a value into a field, an exec edge leads execution, a reference is a link without data movement, for example a foreign key from a table field to a table.
Anchors, ports and routes
Ends snap to a side of the node or to a custom port. Ports are described in the inspector under Ports; the port diamond on the selected node pulls out a live edge, and a port with direction in flips the edge. The input on the query field of a source lets you bind the query text instead of copying it.
The route of an orthogonal edge can be set by hand: Shift-click in connect mode places route points, they snap to horizontal and vertical and follow nodes when dragged. The route guard keeps edges from passing through nodes, and parallel edges are spread apart.
Value bindings
A data edge into a field makes the field read only: it lives from its source and recalculates itself. That is how chains like source → parse → filter → watch are built. Bound and computed values have a viewer in the inspector; large JSON is read without copying.
Exec edges
An exec edge leads from step to step. Branch, sequence, while and foreach loops with break and continue, loop item and index by loop name. Run with the button on the Start node, with the stepper in the toolbar highlighting the active step and the values on edges, or on a server schedule.