Summary

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

Details

Page properties

Content

...	...	@@ -1,28 +1,22 @@
1	1	1 Best Practices
2	2
3		-1.1 Naming Best Practices
	3	+#toc("" "" "")
4	4
5		-1.1.1 Application
6		-* Each application must have its own Space if a user interface is needed.
	5	+1.1 Check for Object existence in Class Sheets documents
7	7
8		-1.1.1 Classes
9		-* Classes must be in the XWiki space
10		-* The name must end with "Class" like "TagClass"
	7	+Class sheet documents should be written using the following construct (this is an example for displaying documents containing XWiki.XWikiUsers objects):
11	11
12		-1.1.1 Macro
13		-* Macro must be in the XWiki space
14		-* The name must end with "Macro" like "TagMacro"
	9	+{code}
	10	+#set($obj = \$doc.getObject("XWiki.XWikiUsers"))
	11	+#if(!$obj)
	12	+ 1 User Sheet
	13	+ This stylesheet must be applied on a document containing a XWiki.XWikiUsers object.
	14	+#else
	15	+ 1 $msg.get("userProfile", [$xwiki.getUserName($doc.fullName, false)])
	16	+ ...
	17	+#end
	18	+{code}
15	15
16		-1.1.1 Sheets
17		-* Sheets must be in the XWiki space
18		-* The name must end with "Sheet" like "TagSheet"
	20	+#info("The 'if' tests first for the non existence. This is so that XWiki extract the title from the ~~1 User Sheet~~, which is a proper title to display when viewsing the sheet page, instead of the computed name which will usually display something wrong.")
19	19
20		-1.1.1 Templates
21		-* Templates must be in the XWiki space
22		-* The name must end with "Templates" like "TagTemplates"
23	23
24		-1.1.1 Objects
25		-* Objects must be in their own space
26		-
27		-<span style="background-color:yellow">TODO: Explain the reasons behind these practices</span>
28		-