Basics: XWiki's main concepts

bring bugfixes but it also come with a new rendering Syntax variants concept and new experimental Live

with a new rendering Syntax variants concept and new experimental Live Data tools (but not used in

explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains

explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains

retro-compatibility with many existing features and applications we had to keep the concepts of "Page

the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this: we had some

, this relationship is crucial. The introduction of the Nested Pages concept In XWiki 7.2, due to frequent users

retro-compatibility with many existing features and applications we had to keep the concepts of "Page

creators. == Detailed Explanations == Before the introduction of the Nested Pages concept (in 7.2

concept === In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces

page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10

page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10

8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's

support the concept of managed dependencies. Its the same idea than Maven's {{code

. 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

:34 <cjd> has quit 03:38 <daemoen> did 7.* replace the concept of spaces with 'subwikis' ? I can't

:34 <cjd> has quit 03:38 <daemoen> did 7.* replace the concept of spaces with 'subwikis' ? I can't

about something.. Can I still use spaces in 7.4? I actually could use the concept. 13:46 <vmassol

defeats the purpose of space as a more top level context container. Foswiki also had the webs concept for

confuse everyone else 14:11 <vmassol> (since you'd need to explain the concept of spaces and how it's

about something.. Can I still use spaces in 7.4? I actually could use the concept. 13:46 <vmassol

defeats the purpose of space as a more top level context container. Foswiki also had the webs concept for

confuse everyone else 14:11 <vmassol> (since you'd need to explain the concept of spaces and how it's

<tmortagne> TranslationBundle API have the concept of priority but all wiki based bundle provide the same

> (10:58:47 AM) tmortagne: TranslationBundle API have the concept of priority but all wiki based bundle

<tmortagne> TranslationBundle API have the concept of priority but all wiki based bundle provide the same

> (10:58:47 AM) tmortagne: TranslationBundle API have the concept of priority but all wiki based bundle