Changes for page Best Practices

<
From version
edited by Eduard Moraru
on 2014/10/17
To version
edited by Vincent Massol
on 2015/09/08
>
Change comment: Minor reword

Details

Page properties
Author
 ... ... @@ -1,1 +1,1 @@ 1 -XWiki.enygma 1 +XWiki.VincentMassol
Content
 ... ... @@ -7,10 +7,10 @@ 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