Changes for page Data Model

Last modified by Vincent Massol on 2023/12/01

<
From version < 29.1 >
edited by Marius Dumitru Florea
on 2012/11/26
To version < 29.2 >
edited by Manuel Smeria
on 2013/02/20
>
Change comment: minor fixes

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mflorea
1 +XWiki.ManuelSmeria
Content
... ... @@ -8,10 +8,10 @@
8 8  
9 9  If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same.
10 10  
11 -; **Classes**
11 +; Classes
12 12  : An XWiki class is like a template that defines a unique type of object. It defines what properties an object can have. When you define a custom class, you are saying that your application may need to create one or many objects (instances) of that class. The class itself is like a cookie cutter and the objects are unique instances of that class. So, in this analogy, if the class is the cookie cutter, the objects are the cookies (and we are talking about real edible cookies in this analogy; not Web cookies).
13 13  : A class is attached to a page. There can be at most one class per page. The class name is the name of the document it is attached to.
14 -; **Properties**
14 +; Properties
15 15  : Properties are the characteristics that an object can have. In a class definition, the properties define the data fields that each unique instance of the class can have values for. Properties have displayers which control how the property value is displayed in view or edit mode. Some displayers use advanced pickers to help you input a valid property value.
16 16  : XWiki currently supports the following kinds of properties (data types):
17 17  
... ... @@ -34,7 +34,7 @@
34 34  * //Computed pseudofield// (new in 4.2M3)
35 35  
36 36  : Starting with version 4.3M2 you can define [[your own property types>>CreatingNewXClassPropertyTypes]].
37 -; **Objects**
37 +; Objects
38 38  : Objects are unique instances of a class with unique values defined for each of the properties that make up the class.
39 39  : An object is attached to a specific page. Each page can have multiple objects.
40 40  : Using objects, you insert **structured** information in the wiki, while in a traditional wiki you can only enter unstructured information (plain text). This is one of the reasons why XWiki is a second generation wiki.

Get Connected