Learn about the concepts and benefits of Blueprint Editor and how it differs from node programming.
Basic concept
Blueprint Editor is commonly referred to as Visual Programming or Flow-Based Programming. It defines interactions between layers through visual connections.
Benefits
-
Unlike node programming, Blueprint Editor ensures real-time and synchronization of interaction and data.
-
Blueprint Editor supports data request merging and data distribution.
-
Blueprint Editor can be modularized and split to focus on a single interaction link. You do not need to organize and standardize code. You only need to focus on business rules and interaction requirements.
-
Blueprint Editor supports original components and third-party components, making it developer-friendly.
ImportantThird-party widgets developed by users must comply with the developer standards.
Differences between Blueprint Editor and Node Programming
|
Node programming |
Blueprint Editor |
Remarks |
|
Triggers added to the canvas |
Upgraded to Branch Decision. |
In Blueprint Editor, the trigger name is retained in the node name. |
|
Converters added to the canvas |
Upgraded the logical node to Serial Data Processing Node. |
In Blueprint Editor, the converter name is retained in the node name. |
|
Left-side layer pane |
Added Nodes pane, where only the widgets added from Canvas Editor are displayed. If an added widget is removed from Blueprint Editor, this widget is marked with a red exclamation point and its configured interactions become invalid. |
None. |
|
Left-side rule template |
|
None. |
|
Preview page in the lower-right corner of the node programming page |
The preview function is now integrated with Canvas Editor. |
None. |
|
Application function key in the upper-right corner of the node programming page |
The application key function is integrated with the preview page function. Changes take effect immediately without clicking the application function key. |
None. |
|
View logs |
Upgraded to Debugging Preview Guide. |
None. |