Codaform
EN
Download
The Codaform handbook

The documentation articles are available in English.

Nodes

All graph node types

This reference lists the node families Codaform currently creates, restores or derives in Parameter Graph. Compatibility aliases used by older saved graphs are not separate user tools.

Where to find it
Parameter Graph toolbar, Designer object add/focus actions, recovered patterns and ports
When to use it
Understanding what each graph card represents before wiring it
On this page

Step by step

  1. Start with the node family that owns the information: Value for a public number, Object for geometry, Math/IF for rules, Pattern for repetition, Port for connections and Anchor for geometric following.
  2. Connect only compatible output-to-input sockets.
  3. Use the specialised article for the node when you need its full workflow.

Value and calculation

Parameter / Value Node stores a named public value. Equation / Math calculates a Result. Condition / IF exposes TRUE and VALUE outputs. ChooseSize performs table-style size lookup; TableLookup is retained as a compatibility/automatic lookup kind where older/imported graph state uses it.

Geometry

Object and ObjectInput represent Designer geometry/properties. ComponentCard represents an imported/library/custom component through its exposed public inputs rather than every internal source leaf.

Patterns and Booleans

RepeatCircle describes circular repetition. ArrayPattern represents remembered Designer Rectangular/Polar arrays. BooleanPatternIntent summarises how a stored pattern participates in a Boolean result.

Connections and relationships

Port represents a Designer port. PortRecipe represents reusable port logic. Anchor represents a Base/Follower geometric relationship.

Saved compatibility names

Older/restored state may contain aliases such as ValueNode, PARAMETER or NODE. The restore path normalises those into the current graph behaviour; they are not extra toolbar commands users need to learn.

Keep in mind

  • If a graph card appears automatically after adding an imported object or recovering a pattern, identify it by its category/header before deciding whether it should be public or hidden inside a layer.

Keep building

Documentation