Changes between Version 3 and Version 4 of code/howto/ClassHierarchy

Timestamp:

Apr 12, 2017, 11:44:25 PM (8 years ago)

Author:

landauf

Comment:

fixed links

code/howto/ClassHierarchy

@@ -1 +1 @@
 = HowTo: Adding a new class to the hierarchy =
-[[TracNav(TracNav/TOC_Development)]]
 [[TOC]]
 
-The class hierarchy in Orxonox is controlled by [wiki:Identifier Identifiers]. Every class has it's identifier. This page explains how a new class is added correctly to the class hierarchy.
+The class hierarchy in Orxonox is controlled by [wiki:doc/Identifier Identifiers]. Every class has it's identifier. This page explains how a new class is added correctly to the class hierarchy.
 
 Features available to classes in the hierarchy:
  * [wiki:howto/Identifier Identifier]
- * [wiki:Factory Factory]
+ * [wiki:doc/Factory Factory]
  * [wiki:howto/Iterator ObjectLists]
  * [wiki:howto/ConfigValue Config-Values]
@@ -14 +13 @@
 
 == Objects ==
-If you want to create a new object (an object in the sense of a game-related class), you have to inherit directly or indirectly from [wiki:BaseObject] and call '''RegisterObject('''''ClassName''''')''' (see [wiki:CoreIncludes]) in the constructor of this class.
+If you want to create a new object (an object in the sense of a game-related class), you have to inherit directly or indirectly from [wiki:doc/BaseObject] and call '''RegisterObject('''''ClassName''''')''' (see [wiki:doc/CoreIncludes]) in the constructor of this class.
 
-If you want this class to be [wiki:Loader loadable] from an [wiki:XMLPort XML-file], add '''CreateFactory('''''ClassName''''')''' outside of the code. This creates a mapping between the string "ClassName" and the class itself (see [wiki:Factory]).
+If you want this class to be [wiki:doc/Loader loadable] from an [wiki:doc/XMLPort XML-file], add '''CreateFactory('''''ClassName''''')''' outside of the code. This creates a mapping between the string "ClassName" and the class itself (see [wiki:doc/Factory]).
 
 *.h file:
@@ -53 +52 @@
 
 == Interfaces ==
-Interfaces in Orxonox aren't objects by themselfes, but provide functions and features for real objects. Those objects inherit from the interfaces, additionally to [wiki:BaseObject] (or a derivative).
+Interfaces in Orxonox aren't objects by themselfes, but provide functions and features for real objects. Those objects inherit from the interfaces, additionally to [wiki:doc/BaseObject] (or a derivative).
 
-Interfaces have to inherit virtually from [wiki:OrxonoxClass] and call '''RegisterRootObject('''''InterfaceName''''')''' in the constructor.
+Interfaces have to inherit virtually from [wiki:doc/OrxonoxClass] and call '''RegisterRootObject('''''InterfaceName''''')''' in the constructor.
 
 *.h file: