<
From version < 17.1 >
edited by Silvia Macovei
on 2010/02/25
To version < 18.1 >
edited by Silvia Macovei
on 2010/02/25
>
Change comment: Fixed Title; Fixed Definitions

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +XWiki Data Model
Content
... ... @@ -1,5 +3,3 @@
1 -= XWiki Data Model =
2 -
3 3  XWiki is not just your average wiki engine; it exposes a flexible data model that can be leveraged at the presentation level. Combined with its powerful presentation level scripting capabilities, XWiki's data model can help you build simple to complex Web applications with little or no need to access the XWiki core. In other words, you can build custom applications through the XWiki web interface without having to compile, package, and deploy software components.
4 4  
5 5  This area explains XWiki's data model of Classes, Properties, and Objects for those users who want to build applications primarily at the presentation level. It will help you understand how you can achieve significant features by programming at this level alone.
... ... @@ -6,38 +6,33 @@
6 6  
7 7  For information about XWiki's underlying database schema (tables and fields), see: [[XWiki's Database Schema>>DevGuide.DatabaseSchema]].
8 8  
9 -== XWiki Classes, Objects, and Properties ==
7 += XWiki Classes, Objects, and Properties =
10 10  
11 11  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.
12 12  
13 -{{html clean="false" wiki="true"}}
14 -<dl>
15 -<dt>**Classes**</dt>
16 -<dd>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).</dd>
17 -<dd>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.</dd>
18 -<dt>**Properties**</dt>
19 -<dd>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.</dd>
20 -<dd>
21 -XWiki currently supports the following kinds of properties (datatypes) which will be explained later in greater detail:
22 -* Number
23 -* String
24 -* TextArea
25 -* Password
26 -* Boolean
27 -* Static List
28 -* Database List
29 -* Database Tree List
30 -* Date
31 -* User List
32 -* Group List
33 -<p/>
34 -</dd>
35 -<dt>**Objects**</dt>
36 -<dd>Objects are unique instances of a class with unique values defined for each of the properties that make up the class.</dd>
37 -<dd>An object is attached to a specific page. Each page can have multiple objects.</dd>
38 -<dd>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.</dd>
39 -</dl>
40 -{{/html}}
11 +; **Classes**
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 +: 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 +\\
15 +; **Properties**
16 +: 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.
17 +: XWiki currently supports the following kinds of properties (datatypes) which will be explained later in greater detail:
18 +* //Number//
19 +* //String//
20 +* TextArea//
21 +* //Password//
22 +* //Boolean//
23 +* //Static List//
24 +* //Database List//
25 +* //Database Tree List//
26 +* //Date//
27 +* //User List//
28 +* //Group List//
29 +\\
30 +; **Objects**
31 +: Objects are unique instances of a class with unique values defined for each of the properties that make up the class.
32 +: An object is attached to a specific page. Each page can have multiple objects.
33 +: 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.
41 41  
42 42  //In summary//:
43 43  

Get Connected