Namespace - Revision history

JKN at 11:09, 24 April 2013

2013-04-24T11:09:38Z

JKN: /* Usage in {{UBIK}} */

2013-01-23T11:23:20Z

‎Usage in {{UBIK}}

JKN at 11:21, 23 January 2013

2013-01-23T11:21:43Z

MLA at 12:55, 31 January 2012

2012-01-31T12:55:46Z

MLA at 16:24, 18 January 2012

2012-01-18T16:24:37Z

MLA: Created page with "A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An identifier defined in a namespace..."

2012-01-18T16:21:47Z

Created page with "A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An Identifier defined in a namespace..."

New page

A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An [[identifier]] defined in a namespace is associated only with that namespace. The same identifier can be independently defined in multiple namespaces. That is, the meaning associated with an identifier defined in one namespace may or may not have the same meaning as the same identifier defined in another namespace.

For example, Bill works for company X and his employee ID is 123. Jane works for company Y and her employee ID is also 123. The reason Bill and Jane can be identified by the same ID number is because they work for different companies. The different companies in this case would symbolize different namespaces. There would be serious confusion if the two people worked for the same company, and still had the same employee ID. For instance, a paycheck issued to employee ID 123 would not identify which person should receive the check.

In large computer programs or documents it is not uncommon to have hundreds or thousands of identifiers. Namespaces provide a mechanism for hiding local identifiers. They provide a means of grouping logically related identifiers into corresponding namespaces, thereby making the system more modular.

<br>Namespaces are stored on every [[Metaobject]].
The Metaobjects´ translation process reads the namespaces and attaches it to the standard namespace („UBIK.Runtime“ or „UBIK.Runtime.UI“).
In the [[treeview]] the [[views]] [[Inheritance]] and [[Contentview]] are getting grouped and sorted by namespace.

===Namespaces for systemcontentobjects===
Every systemcontentobject owns or is able to own the property namespace. The name of this property is given to the object as a namespace.
If the value is empty or the property does not exist, the metaobjects´ namespace will be generated.
It is also possible, that objects do have an empty namespace property.
The systemcontentobjects will be sorted via namespace and displayed in the [[Contentview]].

===Namespaces for standardcontentobjects===
Standardmäßig liefert ein Contentobjekt einen Leerstring als Namespace. Bei Bedarf kann einem Contentobjekt eine Property „NAMESPACE“ verpasst werden. In diesem Fall liefert das Contentobjekt dann den Wert dieses Properties als seinen Namespace. DAVON SOLLTE ABER ABSTAND GENOMMEN WERDEN.

← Older revision		Revision as of 11:09, 24 April 2013
Line 1:		Line 1:
	==Basic definition==		==Basic definition==
−	A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An defined in a namespace is associated only with that namespace. The same identifier can be independently defined in multiple namespaces. That is, the meaning associated with an identifier defined in one namespace may or may not have the same meaning as the same identifier defined in another namespace.	+	A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An object defined in a namespace is associated only with that namespace. The same identifier can be independently defined in multiple namespaces. That is, the meaning associated with an identifier defined in one namespace may or may not have the same meaning as the same identifier defined in another namespace.

@@ Line 8: / Line 8: @@
 ==Usage in {{UBIK}}==
-Namespaces are stored on the Namespace property of several {{UBIK}} class types, such as [[MetaClass|MetaClasses]]. While there is no direct functionality behind this property, some controls in [[{{UBIK}} Studio]] use it for structuring purposes, i.e. the [[Class Browser]].
+Namespaces are stored on the Namespace property of several {{UBIK}} class types, such as [[MetaClass|MetaClasses]]. While there is no direct functionality behind this property, some controls in [[UBIK_Studio_Basics|{{UBIK}} Studio]] use it for structuring purposes, i.e. the [[Class Browser]].
 [[Category:UBIK]]

@@ Line 1: / Line 1: @@
-A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An [[identifier]] defined in a namespace is associated only with that namespace. The same identifier can be independently defined in multiple namespaces. That is, the meaning associated with an identifier defined in one namespace may or may not have the same meaning as the same identifier defined in another namespace.
+==Basic definition==
@@ Line 6: / Line 7: @@
 In large computer programs or documents it is not uncommon to have hundreds or thousands of identifiers. Namespaces provide a mechanism for hiding local identifiers. They provide a means of grouping logically related identifiers into corresponding namespaces, thereby making the system more modular.
-<br>Namespaces are stored on every [[Metaobject]].
+==Usage in {{UBIK}}==
-The Metaobjects´ translation process reads the namespaces and attaches it to the standard namespace („UBIK.Runtime“ or „UBIK.Runtime.UI“).
+Namespaces are stored on the Namespace property of several {{UBIK}} class types, such as [[MetaClass|MetaClasses]]. While there is no direct functionality behind this property, some controls in [[{{UBIK}} Studio]] use it for structuring purposes, i.e. the [[Class Browser]].
-In the [[treeview]] the [[views]] [[Inheritance]] and [[Contentview]] are getting grouped and sorted by namespace.
 [[Category:UBIK]]

← Older revision		Revision as of 12:55, 31 January 2012
Line 20:		Line 20:
	If necessary, the property namespace can be attached to a contentobject. In this case the returnvalue is the properties value.		If necessary, the property namespace can be attached to a contentobject. In this case the returnvalue is the properties value.
	''It is recommended to not use this type of implementation.''		''It is recommended to not use this type of implementation.''
		+
		+	[[Category:UBIK]]

← Older revision		Revision as of 16:24, 18 January 2012
Line 17:		Line 17:

	===Namespaces for standardcontentobjects===		===Namespaces for standardcontentobjects===
−	~~Standardmäßig liefert ein Contentobjekt einen Leerstring als Namespace~~. ~~Bei Bedarf kann einem Contentobjekt eine Property „NAMESPACE“ verpasst werden~~. In ~~diesem Fall liefert das Contentobjekt dann den Wert dieses Properties als seinen Namespace~~. ~~DAVON SOLLTE ABER ABSTAND GENOMMEN WERDEN~~.	+	The namespace of a contentobject is default a emptystring.
		+	If necessary, the property namespace can be attached to a contentobject. In this case the returnvalue is the properties value.
		+	''It is recommended to not use this type of implementation.''