Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Kulagin
	1	+XWiki.ThomasMortagne

Content

...	...	@@ -10,7 +10,7 @@
10	10
11	11	= XWiki Classes, Objects, and Properties =
12	12
13		-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.
	13	+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.
14	14
15	15	; Classes
16	16	: 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).
...	...	@@ -23,7 +23,7 @@
23	23	(((
24	24	|= Field Type|= Since Version |= Description |= Screenshots
25	25	|//String//| |Allows to store and display one line texts |
26		-|//TextArea//| |Allows to store and display large text fields (text and wysiwyg)|
	26	+|[[//TextArea//>>TextArea]]| |Allows to store and display large text fields (text and wysiwyg)|
27	27	|//Number//| |Allows to store and display Numbers of type integer,long,float,double|
28	28	|//Password//| |Allows to store password fields which can be encrypted or hashed |
29	29	|//EMail//|4.2M3 |Allows to store email fields that can be obfuscated at display time |