Changes for page Data Model

Last modified by Vincent Massol on 2023/12/01

<
From version < 27.1 >
edited by Marius Dumitru Florea
on 2012/11/26
To version < 28.1 >
edited by Marius Dumitru Florea
on 2012/11/26
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,8 +12,8 @@
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 14  ; **Properties**
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.
16 -: XWiki currently supports the following kinds of properties (datatypes) which will be explained later in greater detail:
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 +: XWiki currently supports the following kinds of properties (data types):
17 17  
18 18  * //Number//
19 19  * //String//

Get Connected