Search: concept

> Invoice1, Invoice2 15:53 <vmassol> Client 2 > Invoice1 15:54 <vmassol> also don't forget the concept of

must explain the nested concept to my boss 15:57 <vmassol> but it won't be simpler at all 15:58

> Invoice1, Invoice2 15:53 <vmassol> Client 2 > Invoice1 15:54 <vmassol> also don't forget the concept of

must explain the nested concept to my boss 15:57 <vmassol> but it won't be simpler at all 15:58

- (14:18): lucaa: it is, the concept is the same vmassol - (14:18): ask ciprian I'm sure he'll tell you he copied the concept from the current xwiki sas ologo tmortagne - (14:18): IMO 15 is way too close

one, the concept is different vmassol - (14:19): very different vmassol - (14:19): in our case it

- (14:18): lucaa: it is, the concept is the same vmassol - (14:18): ask ciprian I'm sure he'll tell you he copied the concept from the current xwiki sas ologo tmortagne - (14:18): IMO 15 is way too close

one, the concept is different vmassol - (14:19): very different vmassol - (14:19): in our case it

Groovy too but it's about the same concept since it's all Java objects) 15:10 <Slashman> I have some java

concept officially 15:16 <tmortagne> but on your side you can do whatever you want 15:16 <Slashman> hm ok

XWiki component concept anyway which you will pretty much have to use in a java extension 15:22

Groovy too but it's about the same concept since it's all Java objects) 15:10 <Slashman> I have some java

concept officially 15:16 <tmortagne> but on your side you can do whatever you want 15:16 <Slashman> hm ok

XWiki component concept anyway which you will pretty much have to use in a java extension 15:22

:37 <vmassol> basically transforming the old hardcoded concept of enteprrise into flavors 12:37

:37 <vmassol> basically transforming the old hardcoded concept of enteprrise into flavors 12:37

the concept of space at some point (and also nested spaces) 14:51 <vmassol1> right now we just have

the concept of space at some point (and also nested spaces) 14:51 <vmassol1> right now we just have

will try and do a little more research about this concept and the project ofcourse. :P 15:59

will try and do a little more research about this concept and the project ofcourse. :P 15:59

XWiki platform which does not link the user-defined tags to a concept. A semantic tag will preserve the

a.selected-tag:visited { color: #ccc; } .tag-concept-link { padding: 0.5em 2em 0.5em 0; background: url

we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent

inside other wiki pages. More specifically we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent/Child relationship since it was too complex for end

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

basic help concepts. The left panels area also showcases now the 'Navigation' panel, while the right

basic help concepts. The left panels area also showcases now the 'Navigation' panel, while the right