Node Socket Shapes Design [Proposal] #127106

New Issue

Jacques Lucke · 2024-09-03T15:30:13+02:00

Jacques Lucke commented

2024-09-03 15:30:13 +02:00

This problem is described this a blog post.

Shape in Prototype	Input Meaning	Output Meaning
	Multiple Supported Types	Multiple Possible Types
	Requires Single Value	Is Single Value
	Requires Field	Is Field
	Requires Grid	Is Grid

Still need a name for these differences. Currently I call it the Structure Type.
Structure type of group inputs.
- By default it is automatically determined if possible.
- Can be choosen manually.
Structure type of group outputs.
- Currently, I think it's possible to automatically determine it in all cases.
- If not, we need the same dropdown for outputs too.
There is no visible inferencing between nodes.
- E.g. currently the math node changes its socket shapes depending on what you connect. That would not happen anymore.
- The socket shapes describe the behavior of a node on its own.
- There is automatic inferencing for the group inputs/outputs though.
The link visualization of fields can still work as before.
- It's somewhat nice to not communicate the field state twice (before the diamond shape and dashed lines communicated pretty much the same).
For field inputs, there is no difference anymore between sockets that have a default field value and those that don't like we had in the Set Position node.
- This may require a new visualization, or we say that socket inspection is good enough.
Actual socket shapes (besides what is used in the prototype).
- For single values we could start using line sockets based on a design by William Reynish.
- If we use a new socket shape for single values, then we could use the circle for "dynamic" types.
  - This also has the advantage that many nodes that use the circle socket in shader/compositor nodes could keep using it.
  - Need to think about whether it's fine to change geometry/data-block/shader(?) sockets to use the thin socket too.
- The diamond shape for fields is probably good to keep.
- Still need proper socket shapes for Volume Grid, List and Image (+ Single?).

This problem is described [this](https://code.blender.org/2024/05/geometry-nodes-workshop-may-2024/#socket-shapes) a blog post. | Shape in Prototype | Input Meaning | Output Meaning | | -------------------------------------------------- | ------------------------ | ----------------------- | | ![image](/attachments/6a135c42-ed00-4e50-98aa-4b1108280ce5) | Multiple Supported Types | Multiple Possible Types | | ![image](/attachments/7bb70584-b016-4a6d-85a3-6a841ba6da14) | Requires Single Value | Is Single Value | | ![image](https://hackmd.io/_uploads/BJLc7dEnA.png) | Requires Field | Is Field | | ![image](https://hackmd.io/_uploads/SJuf4O4n0.png) | Requires Grid | Is Grid | * Still need a name for these differences. Currently I call it the **Structure Type**. * Structure type of **group inputs**. * ![image](https://hackmd.io/_uploads/BJOKVdE3C.png) * By default it is automatically determined if possible. * Can be choosen manually. * Structure type of **group outputs**. * Currently, I think it's possible to automatically determine it in all cases. * If not, we need the same dropdown for outputs too. * There is *no* visible **inferencing** between nodes. * E.g. currently the math node changes its socket shapes depending on what you connect. That would not happen anymore. * The socket shapes describe the behavior of a node on its own. * There *is* automatic inferencing for the group inputs/outputs though. * The **link visualization** of fields can still work as before. * It's somewhat nice to not communicate the field state twice (before the diamond shape and dashed lines communicated pretty much the same). * For field inputs, there is no difference anymore between sockets that have a **default field value** and those that don't like we had in the Set Position node. * ![image](https://hackmd.io/_uploads/rkU4POEhA.png) * This may require a new visualization, or we say that socket inspection is good enough. * Actual **socket shapes** (besides what is used in the prototype). * For single values we could start using **line** sockets based on a [design](https://projects.blender.org/blender/blender/issues/74967) by William Reynish. * ![image](https://hackmd.io/_uploads/HklB8uEhR.png) * If we use a new socket shape for single values, then we could use the **circle** for "dynamic" types. * This also has the advantage that many nodes that use the circle socket in shader/compositor nodes could keep using it. * Need to think about whether it's fine to change geometry/data-block/shader(?) sockets to use the thin socket too. * The **diamond** shape for fields is probably good to keep. * Still need proper socket shapes for `Volume Grid`, `List` and `Image` (+ `Single`?).

image.png

499 B

image.png

641 B

image.png

1.1 KiB