Node - Revision history

Dgreenwood: Changed redirect target from Node Tree to Node Tree (UI Element)

2024-09-26T19:16:50Z

Changed redirect target from Node Tree to Node Tree (UI Element)

← Older revision		Revision as of 14:16, 26 September 2024
Line 1:		Line 1:
	#REDIRECT [[Node Tree]]		#REDIRECT [[Node Tree (UI Element)]]

Dgreenwood: Changed redirect target from Grooper Node to Node Tree

2024-09-26T19:16:33Z

Changed redirect target from Grooper Node to Node Tree

← Older revision		Revision as of 14:16, 26 September 2024
Line 1:		Line 1:
	#REDIRECT [[~~Grooper~~ Node]]		#REDIRECT [[Node Tree]]

Dgreenwood: Redirected page to Grooper Node

2022-12-09T21:48:37Z

Redirected page to Grooper Node

← Older revision		Revision as of 16:48, 9 December 2022
Line 1:		Line 1:
	~~<onlyinclude>~~		#REDIRECT [[Grooper Node]]
	~~<blockquote style="font-size:14pt">~~
	~~Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.~~
	~~</blockquote>~~

	Nodes pass information to and from each other through "[[Inheritance\|inheritance]]". The [[Parent\|parent]] node dictates inheritance. It controls what [[Child\|child]] objects can be created underneath it, as well as what information is passed to and from the parent and child nodes.

	~~In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as~~ [[Grooper Node]]s.
	~~</onlyinclude>~~

Dgreenwood at 15:56, 23 November 2020

2020-11-23T15:56:50Z

← Older revision		Revision as of 10:56, 23 November 2020
Line 4:		Line 4:
	</blockquote>		</blockquote>

	In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s .		Nodes pass information to and from each other through "[[Inheritance\|inheritance]]". The [[Parent\|parent]] node dictates inheritance. It controls what [[Child\|child]] objects can be created underneath it, as well as what information is passed to and from the parent and child nodes.

			In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s.
	</onlyinclude>		</onlyinclude>

Dgreenwood at 19:36, 27 October 2020

2020-10-27T19:36:26Z

← Older revision		Revision as of 14:36, 27 October 2020
Line 1:		Line 1:
	<onlyinclude>		<onlyinclude>
			<blockquote style="font-size:14pt">
	Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.		Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.
			</blockquote>

	In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s.		In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s .
	</onlyinclude>		</onlyinclude>

Dgreenwood at 19:18, 27 October 2020

2020-10-27T19:18:54Z

← Older revision		Revision as of 14:18, 27 October 2020
Line 1:		Line 1:
			<onlyinclude>
	Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.		Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.

	In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s.		In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s.
			</onlyinclude>

Configadmin at 18:56, 27 December 2019

2019-12-27T18:56:36Z

← Older revision		Revision as of 13:56, 27 December 2019
Line 1:		Line 1:
	Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. ~~Nodes~~ and their properties are stored in the database connected to a [[Grooper Repository]].		Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.

			In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]]. Nodes may also be referred to as [[Grooper Node]]s.

Configadmin at 18:35, 27 December 2019

2019-12-27T18:35:45Z

← Older revision		Revision as of 13:35, 27 December 2019
Line 1:		Line 1:
	Any item in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. Nodes and their properties are stored in the database connected to a [[Grooper Repository]]		Any single item (or [[Object]]) in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. Nodes and their properties are stored in the database connected to a [[Grooper Repository]].

Configadmin: Created page with "Any item in the Node Tree. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. Nodes and their properties are stor..."

2019-12-27T18:24:47Z

Created page with "Any item in the Node Tree. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. Nodes and their properties are stor..."

New page

Any item in the [[Node Tree]]. Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree. Nodes and their properties are stored in the database connected to a [[Grooper Repository]]