Search: concept

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

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.

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

Getting to know XWiki Track 1: Understand XWiki concepts of XClass & XObjects Track 2: Extend your application Track 3: Styling XWiki Start contributing Track 4: Report or find an issue Track 5: Contribute to the core Future tracks to document: Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) Track: Contribute to an existing extension Track: Contribute a new extension Track: Add translations Other resources: Getting started with XWiki for extension developers.

= Getting to know XWiki = * Track 1: [[Understand XWiki concepts of XClass & XObjects>>TrackXObjects]] * Track 2: [[Extend your application>>TrackMacro]] * Track 3: [[Styling XWiki>>TrackStyling]] = Start contributing = * Track 4: [[Report or find an issue>>TrackIssues]] * Track 5: [[Contribute to the core>>TrackCore]] Future tracks to document: * Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) * Track: Contribute to an existing extension * Track: Contribute a new extension * Track: Add translations Other resources: * [[Getting started with XWiki for extension developers>>doc:Drafts.GettingStartedWithXWiki]].

14:03 <tmortagne> one note, don't use "resolve" method if that's the question 14:04 <tmortagne> it depends of the repository you are checking 14:04 <tmortagne> there is various API 14:04 <mflorea> I'm interested only in core or installed 14:04 <tmortagne> if the question is should you use ExtensionManager then the answer is no 14:04 <tmortagne> since ExtensionManager search in remote repositories 14:04 <tmortagne> and it's not what you want 14:04 <mflorea> ok, so I'll use the repo components 14:05 <tmortagne> you should directly use InstalledExtensionRepository and CoreExtensionRepository components 14:05 <mflorea> InstalledExtensionRepository and CoreExtensionRepository 14:05 <mflorea> good 14:05 <tmortagne> it's better to use specific getInstalledExtension API in InstalledExtensionRepository 14:06 <mflorea> got it 14:06 <tmortagne> resolve throw an exception when not finding something 14:06 <tmortagne> which is not great from perf point of view 14:06 <tmortagne> same for CoreExtensionRepository 14:07 <mflorea> oky 14:07 <tmortagne> you will also need to find the namespace where you want to search 14:08 <tmortagne> we don't really have a current namespace concept, there is the namespace for the current wiki, for the current user etc... 14:09 <tmortagne> depends what you want to take into account 14:09 <tmortagne> you can start with the wiki for now I guess 14:09 <mflorea> yes, current wiki 14:17 <cjd> o/t I'm messing around with ckeditor 14:17 <cjd> it's beaurtiful 14:17 <cjd> *beautiful 14:18 <cjd> write a plugin with 20 lines of code, CKEDITOR.addPlugin() *bam* it's registered, +1 more button in the editor 14:20 <silviar1> has joined #xwiki 14:20 <silviar> has quit 14:27 <rihbyne> has quit 14:51 <DarkKnightCZ> is bootstraps webjar somewhere available as project?

14:03 <tmortagne> one note, don't use "resolve" method if that's the question 14:04 <tmortagne> it depends of the repository you are checking 14:04 <tmortagne> there is various API 14:04 <mflorea> I'm interested only in core or installed 14:04 <tmortagne> if the question is should you use ExtensionManager then the answer is no 14:04 <tmortagne> since ExtensionManager search in remote repositories 14:04 <tmortagne> and it's not what you want 14:04 <mflorea> ok, so I'll use the repo components 14:05 <tmortagne> you should directly use InstalledExtensionRepository and CoreExtensionRepository components 14:05 <mflorea> InstalledExtensionRepository and CoreExtensionRepository 14:05 <mflorea> good 14:05 <tmortagne> it's better to use specific getInstalledExtension API in InstalledExtensionRepository 14:06 <mflorea> got it 14:06 <tmortagne> resolve throw an exception when not finding something 14:06 <tmortagne> which is not great from perf point of view 14:06 <tmortagne> same for CoreExtensionRepository 14:07 <mflorea> oky 14:07 <tmortagne> you will also need to find the namespace where you want to search 14:08 <tmortagne> we don't really have a current namespace concept, there is the namespace for the current wiki, for the current user etc... 14:09 <tmortagne> depends what you want to take into account 14:09 <tmortagne> you can start with the wiki for now I guess 14:09 <mflorea> yes, current wiki 14:17 <cjd> o/t I'm messing around with ckeditor 14:17 <cjd> it's beaurtiful 14:17 <cjd> *beautiful 14:18 <cjd> write a plugin with 20 lines of code, CKEDITOR.addPlugin() *bam* it's registered, +1 more button in the editor 14:20 <silviar1> has joined #xwiki 14:20 <silviar> has quit 14:27 <rihbyne> has quit 14:51 <DarkKnightCZ> is bootstraps webjar somewhere available as project?

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!

q=XWIKI-5692#query:XWIKI-5692+page:1+mid:kclhgaponzkw3wc4+state:results 18:53 <tmortagne> I don't think http://jira.xwiki.org/browse/XWIKI-5692 is really true anymore 18:54 <vmassol> ah I introduced some ProtectedBlock concept apparently 18:54 <mflorea1> code macro works fine 18:54 <vmassol> and the icon tx respect them 18:55 <tmortagne> indeed it's still true 18:55 <tmortagne> I tough it was related to it's old use of verbatim block that was removed 18:55 <vmassol> return (block instanceof MacroMarkerBlock) 18:55 <vmassol> && "code".equals(((MacroMarkerBlock) block).getId()); 18:55 <tmortagne> but while using this kind of trick for code macro it's not right for velocity macro wiki=false which have nothing to do with transformations 18:55 <vmassol> inside ProtectedBlockFilter 18:57 <vmassol> so I created XWIKI-5693 for the issue with the code macro and then closed it as won't fix since I introduced the concept of protectedblockfilter 18:57 <mflorea1> Also found this http://jira.xwiki.org/browse/XWIKI-13167 which could also help me, because I could disable the icon trasformation from the URL 18:58 <vmassol> yes 18:58 <mflorea1> so two options: (1) new wiki syntax (2) query string 19:01 <tmortagne> (2) is easier short term and we probably want it anyway 19:02 <tmortagne> as long as we don't have any proper way for a tx to indicate what it modified like macros do you can't risk to execute any other tx in the WYSIWYG 19:03 <tmortagne> in other words any other tx will generate the exact same issue we have with icons right now 19:10 <mflorea1> has quit 19:12 <vmassol> yep 19:15 <vmassol> tearing my hair with the XHTMLWhitespaceXMLFilter code :) not easy to understand 19:15 <vmassol> I wish we could use a generic library instead 19:29 <Enygma`> has quit 19:30 <evalica> has quit 19:37 <tmortagne> has quit 20:09 <cjd> has joined #xwiki 20:30 <sdumitriu> has quit 20:36 <lkrejci> has joined #xwiki 20:45 <sdumitriu> has joined #xwiki 21:07 <cjd> has quit 21:12 <lkrejci> has quit 21:13 <cjd> has joined #xwiki 21:44 <lkrejci> has joined #xwiki 21:52 <lkrejci> has quit 22:00 <mflorea> has joined #xwiki 22:15 <boubou> hey all 22:15 <boubou> Im trying to setup ldap auth with xwiki 22:16 <boubou> im doing that with ldap extension manager 22:17 <boubou> anyone have an config example to show me ?

q=XWIKI-5692#query:XWIKI-5692+page:1+mid:kclhgaponzkw3wc4+state:results 18:53 <tmortagne> I don't think http://jira.xwiki.org/browse/XWIKI-5692 is really true anymore 18:54 <vmassol> ah I introduced some ProtectedBlock concept apparently 18:54 <mflorea1> code macro works fine 18:54 <vmassol> and the icon tx respect them 18:55 <tmortagne> indeed it's still true 18:55 <tmortagne> I tough it was related to it's old use of verbatim block that was removed 18:55 <vmassol> return (block instanceof MacroMarkerBlock) 18:55 <vmassol> && "code".equals(((MacroMarkerBlock) block).getId()); 18:55 <tmortagne> but while using this kind of trick for code macro it's not right for velocity macro wiki=false which have nothing to do with transformations 18:55 <vmassol> inside ProtectedBlockFilter 18:57 <vmassol> so I created XWIKI-5693 for the issue with the code macro and then closed it as won't fix since I introduced the concept of protectedblockfilter 18:57 <mflorea1> Also found this http://jira.xwiki.org/browse/XWIKI-13167 which could also help me, because I could disable the icon trasformation from the URL 18:58 <vmassol> yes 18:58 <mflorea1> so two options: (1) new wiki syntax (2) query string 19:01 <tmortagne> (2) is easier short term and we probably want it anyway 19:02 <tmortagne> as long as we don't have any proper way for a tx to indicate what it modified like macros do you can't risk to execute any other tx in the WYSIWYG 19:03 <tmortagne> in other words any other tx will generate the exact same issue we have with icons right now 19:10 <mflorea1> has quit 19:12 <vmassol> yep 19:15 <vmassol> tearing my hair with the XHTMLWhitespaceXMLFilter code :) not easy to understand 19:15 <vmassol> I wish we could use a generic library instead 19:29 <Enygma`> has quit 19:30 <evalica> has quit 19:37 <tmortagne> has quit 20:09 <cjd> has joined #xwiki 20:30 <sdumitriu> has quit 20:36 <lkrejci> has joined #xwiki 20:45 <sdumitriu> has joined #xwiki 21:07 <cjd> has quit 21:12 <lkrejci> has quit 21:13 <cjd> has joined #xwiki 21:44 <lkrejci> has joined #xwiki 21:52 <lkrejci> has quit 22:00 <mflorea> has joined #xwiki 22:15 <boubou> hey all 22:15 <boubou> Im trying to setup ldap auth with xwiki 22:16 <boubou> im doing that with ldap extension manager 22:17 <boubou> anyone have an config example to show me ?

13:58 <msmeria> for ex. "0 Document(s) installed" 13:58 <tmortagne> you get that message because the UI is looking at old packager for imported document and can't find any 13:58 <tmortagne> the refactoring is not complete yet 13:58 <tmortagne> that's what it's not by default 13:58 <msmeria> I see 13:59 <tmortagne> see jira.xwiki.org/browse/XWIKI-9720 for the list of known limitations 13:59 <tmortagne> in this case it's "the report is directly gathered from PackageAPI" 14:00 <msmeria> yep. got it. thanks for the clarification 14:00 <tmortagne> since it was in blue I did not even seen its was written as an error 14:01 <tmortagne> evalica: the concept of bundled extension does not really exist in XWiki Repository, it's a xwiki.org customization 14:02 <tmortagne> it does not really make sense at generic repository application level 14:02 <evalica> the repository Application equals 'Repository' component?

13:58 <msmeria> for ex. "0 Document(s) installed" 13:58 <tmortagne> you get that message because the UI is looking at old packager for imported document and can't find any 13:58 <tmortagne> the refactoring is not complete yet 13:58 <tmortagne> that's what it's not by default 13:58 <msmeria> I see 13:59 <tmortagne> see jira.xwiki.org/browse/XWIKI-9720 for the list of known limitations 13:59 <tmortagne> in this case it's "the report is directly gathered from PackageAPI" 14:00 <msmeria> yep. got it. thanks for the clarification 14:00 <tmortagne> since it was in blue I did not even seen its was written as an error 14:01 <tmortagne> evalica: the concept of bundled extension does not really exist in XWiki Repository, it's a xwiki.org customization 14:02 <tmortagne> it does not really make sense at generic repository application level 14:02 <evalica> the repository Application equals 'Repository' component?

11:55 <gdelhumeau> the space concept should be hidden in the UI normally 11:55 <vmassol> Enygma`: the alternative is to implement a tree switcher 11:56 <vmassol> (which could be useful) 11:56 <gdelhumeau> and we should create a page admin instead 11:56 <gdelhumeau> when we'll have the page administration the functionnal tests abour space admin wil not be usefull anymore 11:56 <vmassol> I don't see what harm it would do to be able to switch admin page from within the admin 11:57 <vmassol> gdelhumeau: most failing tests are not about that 11:57 <vmassol> hmm maybe they ayre 11:57 <vmassol> *are 11:58 <evalica> since space administration is now 'page administration', the administration should be available in the 'More actions' part of the menu.

16:00 <vmassol> getWikiId has even been introduced in 6.1 16:00 <vmassol> 6.1M1 16:00 <vmassol> xcontext is not deprecated 16:01 <vmassol> so we need to decide if wiki script module is core or not 16:01 <vmassol> (ie it has to be in a most minimal wiki we can make) 16:03 <vmassol> if we say that the wiki concept is core then I guess we should also have it in the core so that velocity pages can using wiki apis 16:03 <gdelhumeau> indeed 16:04 <vmassol> velo scripting that is 16:04 <vmassol> api.XWiki is core ATM so I guess it makes sense that wiki SS should be too 16:17 <vmassol> ok mail ready, sending 16:18 <Enygma`> because we come from a single wiki setup *and* because oldcore is... old and should not be extended, the wiki API is bundled in a separate module and accessible to scripting through a script service, but that does not mean that is does not make it core 16:18 <vmassol> it means we didn't have to make it core 16:18 <vmassol> because it was nicely done separately 16:18 <vmassol> w're just loosing this advnatage 16:18 <Enygma`> it was done separately out of necessity 16:18 <vmassol> it's a bet that we won't need it, which is ok, just makes xwiki more heavywieght as it could be 16:19 <Enygma`> but conceptually it should have been there from the start, IMO 16:19 <vmassol> exactly 16:19 <vmassol> and we're loosing that advatnage 16:19 <vmassol> and tomorrow you're going to say that federations of wikis are core too?

11:55 <gdelhumeau> the space concept should be hidden in the UI normally 11:55 <vmassol> Enygma`: the alternative is to implement a tree switcher 11:56 <vmassol> (which could be useful) 11:56 <gdelhumeau> and we should create a page admin instead 11:56 <gdelhumeau> when we'll have the page administration the functionnal tests abour space admin wil not be usefull anymore 11:56 <vmassol> I don't see what harm it would do to be able to switch admin page from within the admin 11:57 <vmassol> gdelhumeau: most failing tests are not about that 11:57 <vmassol> hmm maybe they ayre 11:57 <vmassol> *are 11:58 <evalica> since space administration is now 'page administration', the administration should be available in the 'More actions' part of the menu.

16:00 <vmassol> getWikiId has even been introduced in 6.1 16:00 <vmassol> 6.1M1 16:00 <vmassol> xcontext is not deprecated 16:01 <vmassol> so we need to decide if wiki script module is core or not 16:01 <vmassol> (ie it has to be in a most minimal wiki we can make) 16:03 <vmassol> if we say that the wiki concept is core then I guess we should also have it in the core so that velocity pages can using wiki apis 16:03 <gdelhumeau> indeed 16:04 <vmassol> velo scripting that is 16:04 <vmassol> api.XWiki is core ATM so I guess it makes sense that wiki SS should be too 16:17 <vmassol> ok mail ready, sending 16:18 <Enygma`> because we come from a single wiki setup *and* because oldcore is... old and should not be extended, the wiki API is bundled in a separate module and accessible to scripting through a script service, but that does not mean that is does not make it core 16:18 <vmassol> it means we didn't have to make it core 16:18 <vmassol> because it was nicely done separately 16:18 <vmassol> w're just loosing this advnatage 16:18 <Enygma`> it was done separately out of necessity 16:18 <vmassol> it's a bet that we won't need it, which is ok, just makes xwiki more heavywieght as it could be 16:19 <Enygma`> but conceptually it should have been there from the start, IMO 16:19 <vmassol> exactly 16:19 <vmassol> and we're loosing that advatnage 16:19 <vmassol> and tomorrow you're going to say that federations of wikis are core too?