Namespaces - Revision history

MLA: Redirected page to Namespace

2012-01-18T16:21:42Z

Redirected page to Namespace

MLA: Blanked the page

2012-01-18T16:21:15Z

Blanked the page

MLA at 16:14, 18 January 2012

2012-01-18T16:14:12Z

MLA at 16:00, 18 January 2012

2012-01-18T16:00:07Z

MLA at 15:57, 18 January 2012

2012-01-18T15:57:08Z

MLA at 15:39, 18 January 2012

2012-01-18T15:39:10Z

MLA at 15:24, 18 January 2012

2012-01-18T15:24:37Z

MLA at 15:23, 18 January 2012

2012-01-18T15:23:33Z

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-13T08:02:37Z

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.

← Older revision	Revision as of 16:21, 18 January 2012
Line 1:	Line 1:
−	+	#redirect [[Namespace]]

← Older revision		Revision as of 16:21, 18 January 2012
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.

−
−	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.

@@ Line 8: / Line 8: @@
 <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 [[Content]] are getting grouped and sorted by namespace.
+In the [[treeview]] the [[views]] [[Inheritance]] and [[Contentview]] are getting grouped and sorted by namespace.
 ===Namespaces for systemcontentobjects===

@@ Line 14: / Line 14: @@
 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
+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.

@@ 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.
-<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“).
-The In der Baumanzeige werden die Objekte  in den Sichten „Inheritance“ und „Content“ gruppiert nach deren Namespace angezeigt.
 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.
@@ Line 8: / Line 6: @@
 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.
-===Namespaces für „System“Contentobjekte===
+<br>Namespaces are stored on every [[Metaobject]].
-Jede Systemcontentobjekt besitzt (bzw. kann besitzen) eine Property „NAMESPACE“. Der Wert dieses Properties wird als Namespace für das Objekt übernommen. Ist der Wert leer (oder das Property fehlt), dann wird der Namespace dessen Metaobjektes angezeigt.
+The Metaobjects´ translation process reads the namespaces and attaches it to the standard namespace („UBIK.Runtime“ or „UBIK.Runtime.UI“).
-Objekte können auch eine leere Namespace Eigenschaft besitzen.
+In the [[treeview]] the [[views]] [[Inheritance]] and [[Content]] are getting grouped and sorted by namespace.
 Die Systemcontentobjekte werden in der Contentanzeige (Baum) gruppiert nach deren Namespace angezeigt.
-===Namespaces für „Standard“Contentobjekte===
+===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.