translations are using the same concepts as the XWiki Java Properties except that the translations

Properties translations are using the same concepts as the [[XWiki Java Properties>>||anchor

. Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object

comment : The combination of *actions* (like <tt>save</tt>) and *request parameters* (like <tt>xredirect</tt>) obviously is a very powerful means to work with XWiki documents. Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?

", or "1" {table} 1.1 Sample use cases TBD. Example to illustrate formentioned concepts. Ex: Ajax

. Editing Pages XWiki Syntax Understanding XWiki Basic Concepts Document Lifecycle URL resolution

XWiki = * [[Basic Concepts >> http://enterprise.xwiki.org/xwiki/bin/view/GettingStarted

(Credit goes to Drupal). XWiki is quite a foreign concept to many people. e.g. people who

, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions

* Knowledge of CSS\r\n* Knowledge of LESS\r\n* Knowledge of Git\r\n* You will encounter concepts like XWiki

will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular

/task/6056420625612800/]]). XWiki is quite a foreign concept to many people. e.g. people who

description : Traditional wikis in which you can enter text and images are no longer the hype. You could even argue that traditional wikis are loosing traction or mindshare. Other concepts have arisen in the past such as CMS (Content Management System) and WCM (Web Content Management). However what user

Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: wiki pages (*.xml files) velocity templates (*.vm files) Strategy Specifically the idea is to be able to write integration tests that use the real code except

{{box cssClass="floatinginfobox" title="**Contents**"}} {{toc/}} {{/box}} = Concept = This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: * wiki pages (##*.xml## files) * velocity templates (##*.vm## files) = Strategy

proposant un runtime web de prototypage ce qui est un concept nouveau et interessant de connaitre pour tout

plate-forme XWiki. Utiliser un plate-forme de wiki est très similaire dans son concept à utiliser un

concepts AWM has made it simple to create your first application but it's cheating a bit since it's doing

the concepts of XClass, XObjects, XProperties, Sheets and Templates. To do that, start by following

Track: Understand XWiki core concepts

>>doc:xwiki:Documentation.DevGuide.Tutorials.CreatingExtensions.WebHome]]. = Task 3: Understand XWiki concepts = AWM has made it simple to create your first

! :) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates

volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english

translation application. The concept seems to work by application version. We need to verity

concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation

on launchpad.net there is a quite extensively developed translation application. The concept seems to work