Summary

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

Details

Page properties

Content

...	...	@@ -7,14 +7,15 @@
7	7	Since xwiki allows you to put code both in wiki pages and in Java you might wonder where you should put your code. Here are some general guidelines:
8	8
9	9	* Don't put "business logic" code in wiki pages. Use Java for that. This gives you nice IDEs, the ability to easily debug the code and the ability to write automated unit tests. Generally speaking it makes it easy on maintenance.
10		-* In general put the minimum amount of scripts in your wiki pages since that makes it harder to maintain.
11		-* The only scripts that you may put in wiki pages are "presentation logic" code.
	10	+* In general put the minimum amount of scripts in your wiki pages since that makes them harder to maintain.
	11	+* The only scripts that you should put in wiki pages (and not in Java code!) are "presentation logic" scripts, i.e. scripts in charge of presenting the data retrieved by using the Java/REST APIs.
12	12
13		-Said differently you should use the [[MVC>>http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller]] approach by separating your Model (what we called "business logic" above) from your View (what we called "presentation logic" above).
	13	+Said differently you should use the [[MVC>>http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller]] pattern by separating your Model (what we called "business logic" above) from your View (what we called "presentation logic" above).
14	14
15	15	= XWiki Application Organization =
16	16
17		-Check the [[Application Development Best Practices document>>ApplicationDevelopmentBestPractices]].
	17	+* [[XWiki Development Team best practices>>dev:Community.ApplicationDevelopmentBestPractices]]
	18	+* [[dev:Drafts.Best Practices XWiki Application Organization]] (proposed by Ludovic Dubost)
18	18
19	19	= Check for Object existence in Class Sheets documents =
20	20
...	...	@@ -32,7 +32,7 @@
32	32	{{/code}}
33	33
34	34	{{info}}
35		-The 'if' tests first for the non existence. This is so that XWiki can 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.
	36	+The 'if' tests first for the non existence. This is so that XWiki can extract the title from the //1 User Sheet//, which is a proper title to display when viewing the sheet page, instead of the computed name which will usually display something wrong.
36	36	{{/info}}
37	37
38	38	= Handling errors when using xredirect for non-Javascript UIs =