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

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.

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.

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

Update [[Wikipedia (en)>>http://en.wikipedia.org/wiki/XWiki]], [[Wikipedia (fr)>>http://fr.wikipedia.org/wiki/XWiki]] and [[Wikipedia (compare wiki software)>>http://en.wikipedia.org/wiki/Comparison_of_wiki_software]] {{warning}}Nothing to do, since Mediawiki's "infobox software" doesn't support the concept of LTS...{{/warning}} * (/) [[Wikimatrix>>http://www.wikimatrix.org/edit/XWiki]] with Ludovic's account * (/) [[Announcement Mail>>ReleasePlans.ReleasePlanHelp||anchor="HAnnouncementMail"]] * (/) [[Announce on Twitter>>ReleasePlans.ReleasePlanHelp||anchor="HAnnounceonTwitter"]] with the [[xwikiorg account>>https://twitter.com/xwikiorg/]] * (/) Update the [[Release Plan page>>ReleasePlans.WebHome||anchor="HNextReleaseManagers"]] to move yourself to the bottom of the list for your next release

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.

09:54 <Denis> for the same reason 09:55 <vmassol> it's your impl that is not going to work 09:55 <vmassol> not the concept 09:55 <vmassol> it just means the impl is not correct 09:55 <Denis> its is for speed and memory 09:55 <vmassol> yes but I doubt that it's a problem 09:55 <Denis> the implementation from Andreas were even worse 09:56 <vmassol> we defiintley need to be able to add and rmoeve rights 09:56 <vmassol> so if the impl cannot do we shouldn't even consider it 09:56 <vmassol> since it's not fulfulling the main reason for the new impl 09:56 <Denis> we could remove rights, but a singe run will keep them 09:56 <vmassol> I'm dispapointed 09:56 <Denis> untill restart 09:57 <vmassol> couldn't you at least keep holes?

09:54 <Denis> for the same reason 09:55 <vmassol> it's your impl that is not going to work 09:55 <vmassol> not the concept 09:55 <vmassol> it just means the impl is not correct 09:55 <Denis> its is for speed and memory 09:55 <vmassol> yes but I doubt that it's a problem 09:55 <Denis> the implementation from Andreas were even worse 09:56 <vmassol> we defiintley need to be able to add and rmoeve rights 09:56 <vmassol> so if the impl cannot do we shouldn't even consider it 09:56 <vmassol> since it's not fulfulling the main reason for the new impl 09:56 <Denis> we could remove rights, but a singe run will keep them 09:56 <vmassol> I'm dispapointed 09:56 <Denis> untill restart 09:57 <vmassol> couldn't you at least keep holes?

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

14:25 <tmortagne> all you have to do with do the Solr request with a locales which is part of the supported locales 14:26 <tmortagne> locales=en will matches only documents you would see if you have en as current locale 14:27 <tmortagne> the "locales" field contains all the supported locales for which the document is the one to show in the UI 14:28 <tmortagne> the fallback is "calculated" during index basically 14:30 <tmortagne> I initially did this so that the main Solr search would look in all the documents you would see with the current locale instead on only the documents explicitly for the current locale 14:30 <tmortagne> so this field is pretty old 14:31 <mflorea> I know it'old 14:34 <mflorea> I though there could be multiple translations of a doc matched by locales=en, but it's not the case 14:35 <tmortagne> "so this field is pretty old" = might have been broken since it is not used anymore in the main UI but it's what it's supposed to do 14:36 <mflorea> it shouldn't be broken, I don't remember touching it, but indeed the search UI doesn't use it 14:37 <tmortagne> anyway import thing is that the concept already exist and just need to check if it still work and fix it otherwise since that would be a regression 14:37 <mflorea> now, another thing that worries me about Solr is sort and pagination performance.

14:25 <tmortagne> all you have to do with do the Solr request with a locales which is part of the supported locales 14:26 <tmortagne> locales=en will matches only documents you would see if you have en as current locale 14:27 <tmortagne> the "locales" field contains all the supported locales for which the document is the one to show in the UI 14:28 <tmortagne> the fallback is "calculated" during index basically 14:30 <tmortagne> I initially did this so that the main Solr search would look in all the documents you would see with the current locale instead on only the documents explicitly for the current locale 14:30 <tmortagne> so this field is pretty old 14:31 <mflorea> I know it'old 14:34 <mflorea> I though there could be multiple translations of a doc matched by locales=en, but it's not the case 14:35 <tmortagne> "so this field is pretty old" = might have been broken since it is not used anymore in the main UI but it's what it's supposed to do 14:36 <mflorea> it shouldn't be broken, I don't remember touching it, but indeed the search UI doesn't use it 14:37 <tmortagne> anyway import thing is that the concept already exist and just need to check if it still work and fix it otherwise since that would be a regression 14:37 <mflorea> now, another thing that worries me about Solr is sort and pagination performance.

I fear not many people will understand either though 19:00 <vmassol> (this concept of repair and what it means) 19:00 <vmassol> they'll just click on repair when they see it :) 19:00 <tmortagne> that's the plan :) 19:00 <vmassol> hopefully that's good enough and they don't need to understand anything more 19:01 <tmortagne> they have a read message and a button talking about repairing it, I guess it's enough for most user 19:01 <vmassol> ok re revapi we know the problem 19:01 <vmassol> https://github.com/revapi/revapi/issues/36#issuecomment-205890553 19:02 <vmassol> lkrejci: :) 19:02 <vmassol> (thanks for checking this out so quickly btw!

I fear not many people will understand either though 19:00 <vmassol> (this concept of repair and what it means) 19:00 <vmassol> they'll just click on repair when they see it :) 19:00 <tmortagne> that's the plan :) 19:00 <vmassol> hopefully that's good enough and they don't need to understand anything more 19:01 <tmortagne> they have a read message and a button talking about repairing it, I guess it's enough for most user 19:01 <vmassol> ok re revapi we know the problem 19:01 <vmassol> https://github.com/revapi/revapi/issues/36#issuecomment-205890553 19:02 <vmassol> lkrejci: :) 19:02 <vmassol> (thanks for checking this out so quickly btw!