Search: concept

{{/version}} = Examples = == Full Examples == * {{scm path="xwiki-platform-core/xwiki-platform-menu/xwiki-platform-menu-test/xwiki-platform-menu-test-docker/src/test/it/org/xwiki/menu/test/ui/MenuIT.java"}}MenuIT{{/scm}} * {{scm path="xwiki-platform-core/xwiki-platform-mail/xwiki-platform-mail-test/xwiki-platform-mail-test-docker/src/test/it/org/xwiki/mail/test/ui/MailIT.java"}}MailIT{{/scm}} == Example 1: Basic test == {{code language="java"}} @UITest public class SeleniumTest { @Test public void test(XWikiWebDriver driver, TestUtils setup) { driver.get("http://xwiki.org"); assertThat(driver.getTitle(), containsString("XWiki - The Advanced Open Source Enterprise and Application Wiki")); driver.findElement(By.linkText("XWiki's concept")).click(); } } {{/code}} == Example 2: Choosing Container + DB + Browser and versions == {{code language="java"}} @UITest(database = Database.MYSQL, databaseTag = "5", servletEngine = ServletEngine.TOMCAT, servletEngineTag = "8", browser = Browser.CHROME) public class MenuIT ...

Here is an example of the minimum maven builds one should run to check a small change in xwiki-platform-flamingo-skin-resources: mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-resources -Pquality mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test -Pintegration-tests,docker The changes are related to the concept of panels, so we also build mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed.

Since these 2 projects contain libraries that are independent of the concept of wikis, this makes it very easy for everyone to use them in their own projects.

The changes are related to the concept of panels, so we also build ##mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker## If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed

Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model.

{{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.

Task 3: Understand XWiki concepts AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

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

Track: Understand XWiki core concepts

= Task 3: Understand XWiki concepts = AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

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

Utiliser un plate-forme de wiki est très similaire dans son concept à utiliser un serveur d'applications. Tout comme les serveurs d'app offrent des services techniques aux applications hébergées, une plate-forme de wiki offre des services de plus haut niveau tels gestion de contenu, moteur de rendu, stockage, éditeur WYSIWYG, gestion des utilisateurs et beaucoup plus.

description : Le concept de Long Tail introduit par Chris Anderson est maintenant bien connu dans le domaine du livre. Ce concept existe également dans le domaine des apps.

Cette presentation apporte un peu de nouveautes en proposant un runtime web de prototypage ce qui est un concept nouveau et interessant de connaitre pour tout bon developeur ou architecte java.

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).

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

15:47 <Pbas> when simple user create a page, by default the new page is created on current "space" 15:48 <vmassol> by default a page is created as a subpage of the current page 15:48 <Pbas> yes then after a while it is messy 15:48 <vmassol> unless the user changes the location in the create dialog 15:48 <vmassol> no 15:48 <vmassol> it's the opposite 15:48 <vmassol> if you create everything at the same level then it's messy 15:49 <Pbas> yes but a normal user didn't think about ordering 15:49 <vmassol> and users have to invent naming conventions 15:49 <vmassol> to differentiate pages 15:49 <vmassol> I don't understand what you mean by ordering 15:49 <vmassol> there's no order between pages 15:50 <tmortagne> Pbas: depends what you call "normal user", you are basically saying that people can't handle folders 15:50 <Pbas> I meanin "ranger" 15:50 <Pbas> "classer" 15:50 <vmassol> so organization 15:50 <vmassol> again one folder is much more messy 15:51 <vmassol> take a drawer at home and put all your invoices into a single drawer 15:51 <vmassol> then dare tell me it's clean and easy to find what you want afterwards :) 15:51 <vmassol> that's why you have different binders 15:51 <vmassol> and different drawers 15:52 <vmassol> I'm not sure why you think that a single level (a la wikipedai) is better 15:52 <vmassol> if you do that you're forcing users to invent categorization 15:52 <vmassol> by creating naming conventions when they create their pages 15:52 <vmassol> Client1Invoice1 15:52 <vmassol> Client1Invoice2 15:52 <vmassol> Client2Invoice1 15:53 <vmassol> instead of Client1 > Invoice1, Invoice2 15:53 <vmassol> Client 2 > Invoice1 15:54 <vmassol> also don't forget the concept of wikis, it's meant to be self organized, if you create too much strucrure you're going to fail and remove serendipity and initiative from people who contribute 15:55 <Pbas> agree it is for this raeson that nested affraid boss 15:55 <Pbas> simple users haven't right enough to create new space on xwiki 7.0.1 15:55 <Pbas> Need news space/folder? ask to advanced user 15:56 <vmassol> as I said it's the same 15:56 <vmassol> at worst you'll have everything at the same level 15:57 <vmassol> with bad naming 15:57 <Pbas> anyway I must explain the nested concept to my boss 15:57 <vmassol> but it won't be simpler at all 15:58 <vmassol> hire me and I'll come do a training in the south :) 15:58 <vmassol> (which would be nice since it's raining here :)) 15:58 <Pbas> ha yes you want send a postcard!

15:47 <Pbas> when simple user create a page, by default the new page is created on current "space" 15:48 <vmassol> by default a page is created as a subpage of the current page 15:48 <Pbas> yes then after a while it is messy 15:48 <vmassol> unless the user changes the location in the create dialog 15:48 <vmassol> no 15:48 <vmassol> it's the opposite 15:48 <vmassol> if you create everything at the same level then it's messy 15:49 <Pbas> yes but a normal user didn't think about ordering 15:49 <vmassol> and users have to invent naming conventions 15:49 <vmassol> to differentiate pages 15:49 <vmassol> I don't understand what you mean by ordering 15:49 <vmassol> there's no order between pages 15:50 <tmortagne> Pbas: depends what you call "normal user", you are basically saying that people can't handle folders 15:50 <Pbas> I meanin "ranger" 15:50 <Pbas> "classer" 15:50 <vmassol> so organization 15:50 <vmassol> again one folder is much more messy 15:51 <vmassol> take a drawer at home and put all your invoices into a single drawer 15:51 <vmassol> then dare tell me it's clean and easy to find what you want afterwards :) 15:51 <vmassol> that's why you have different binders 15:51 <vmassol> and different drawers 15:52 <vmassol> I'm not sure why you think that a single level (a la wikipedai) is better 15:52 <vmassol> if you do that you're forcing users to invent categorization 15:52 <vmassol> by creating naming conventions when they create their pages 15:52 <vmassol> Client1Invoice1 15:52 <vmassol> Client1Invoice2 15:52 <vmassol> Client2Invoice1 15:53 <vmassol> instead of Client1 > Invoice1, Invoice2 15:53 <vmassol> Client 2 > Invoice1 15:54 <vmassol> also don't forget the concept of wikis, it's meant to be self organized, if you create too much strucrure you're going to fail and remove serendipity and initiative from people who contribute 15:55 <Pbas> agree it is for this raeson that nested affraid boss 15:55 <Pbas> simple users haven't right enough to create new space on xwiki 7.0.1 15:55 <Pbas> Need news space/folder? ask to advanced user 15:56 <vmassol> as I said it's the same 15:56 <vmassol> at worst you'll have everything at the same level 15:57 <vmassol> with bad naming 15:57 <Pbas> anyway I must explain the nested concept to my boss 15:57 <vmassol> but it won't be simpler at all 15:58 <vmassol> hire me and I'll come do a training in the south :) 15:58 <vmassol> (which would be nice since it's raining here :)) 15:58 <Pbas> ha yes you want send a postcard!