Child: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
</blockquote> | </blockquote> | ||
New child nodes are created underneath a "[[Parent|parent]]" object in the Node Tree. The parent node determines | New child nodes are created underneath a "[[Parent|parent]]" object in the Node Tree. The parent node determines inheritance for the child node. | ||
* The parent node will always determine what objects can be created as children. For example, a '''Data Table''' can only have '''Data Columns''' as its children. | * The parent node will always determine what objects can be created as children. For example, a '''Data Table''' can only have '''Data Columns''' as its children. | ||
* The parent node may simply be a folder containing child objects, as is the case in a '''Content Model's''' '''Local Resources''' folder. | * The parent node may simply be a folder containing child objects, as is the case in a '''Content Model's''' '''Local Resources''' folder. | ||
Revision as of 15:36, 20 September 2023
In object oriented programing, a child is a class that inherits attributes and functions from a parent class. In terms of a tree structure (like the Grooper Node Tree), a "child" node is an object one level below another node.
New child nodes are created underneath a "parent" object in the Node Tree. The parent node determines inheritance for the child node.
- The parent node will always determine what objects can be created as children. For example, a Data Table can only have Data Columns as its children.
- The parent node may simply be a folder containing child objects, as is the case in a Content Model's Local Resources folder.
- The parent node may have a complex inheritance relationship.
- For example, a Data Type's children Value Readers will pass all results they return to the parent Data Type. Those results will then be collated according to the Data Type's configuration.