...
| Gliffy |
|---|
| |
|---|
| chrome | min |
|---|
| size | 400 |
|---|
| html5 | false |
|---|
| name | unitDatAnatomy |
|---|
|
| There are three types of Ports: - Trigger Port: Trigger the execution of a Unit (= Execute Trigger) or trigger the next Unit which is connected to one of the outgoing Triggers (= Success/Fail Trigger).
See chapter → Unit Triggers & Events. - Input Port: These Ports accept data from the User or other Units. They can also represent the attributes of a Unit. Not all Input Ports can be modified by the User, some of them only accept data from other Units as their input, i.e. a Cable has to be connected to them (for example Structure-based Units). Once a Port is connected with a Cable, it can not be altered by the User anymore.
See chapter → Unit Attributes. - Output Port: These Ports output data and may be connected to other Units.
|
...
Units can roughly be categorized in three types. Of course the exception proves exceptions prove the rule.
| Unit Type | Description | Example |
|---|
| Provider Unit | They only have one or multiple Output Ports and "provide" something. | Variable Getter, System Timestamp |
| Processing Unit | They have one or multiple Input and Output Ports and process or modify their input. | String Replace, String to Time |
| Consumer Unit | They only have one or multiple Input Ports and "consume" data. | Print String, Variable Setter |
Unit Interaction Example
Here 's is a simplified schematic on how Units can interact with each other. Trigger Ports are omitted in this example.
...