Search: concept

Though the mailing list ##[email protected]## is now in "read-only" mode, you can still view its archives either on [[Markmail>>http://xwiki.markmail.org]] or on [[Nabble>>http://xwiki.475771.n2.nabble.com/]]. ))) (% class="col-md-4 col-sm-12" %) ((( [[image:userForumStats.png||class="shadow"]] ))) ))) (% class="row" %) ((( (% class="col-md-8 col-sm-12 text-justify" %) ((( === Introduction of [[Flavors>>xwiki:Documentation.UserGuide.Features.Applications||queryString="#HFlavors"]] === Starting with [[XWiki 9.5.1>>Download.DownloadVersion||queryString="projectVersion=9.5.1"]], we switched from providing the old "XWiki Enterprise" package, with a default set of installed applications to the "Flavors" concept. In XWiki, a flavor is simply a bundle of extensions that serve a particular usage. As an equivalent to XWiki Enterprise, we now release the "[[XWiki Standard>>extensions:Extension.XWiki Standard Flavor]]" flavor that provides the same functionalities as XWiki Enterprise while using this new concept. For more informations, do not hesitate to check out [[Caty's blog post>>Blog.XWiki Enterprise is dead, long live XWiki!]]

For those unfamiliar with the concept, a "flavor" is a collection of extensions corresponding to a specific use case or theme.

Page Index Since we have introduced the concept of Nested Spaces we needed to replace the Space column in the LiveTable with a more generic solution.

{{/warning}} == Page Index == Since we have introduced the concept of Nested Spaces we needed to replace the Space column in the LiveTable with a more generic solution.

answer : Starting with XWiki 7.2, XWiki supports the concept of [[Nested Pages>>Documentation.UserGuide.Features.ContentOrganization.WebHome]].

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

This version mainly introduces various ways of customizing users directory and profiles and it also bring all comments features to annotation (answer, threaded annotation, etc.) by merging the two concepts in one comment with optional precise location.

This version mainly introduces various ways of customizing users directory and profiles and it also bring all comments features to annotation (answer, threaded annotation, etc.) by merging the two concepts in one comment with optional precise location

That said, there are many use cases for workflows and if you need some simple steps, you can implement them in an adhoc way using [[XWiki's concept of Classes and Objects>>Documentation.DevGuide.DataModel]].

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

It also introduces the concept of Reference for any entity of the model and the parser/serializer associated.

We have worked hard during all the summer to finally achieve the introduction of a new concept: Nested Pages. This big change affects both the platform and the user interface, and you will discover many differences while using XWiki.

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 users to have 2 hierarchies: the Space/Page hierarchy and the Parent/Child hierarchy.

We have worked hard during all the summer to finally achieve the introduction of a new concept: **//Nested Pages//**. This big change affects both the platform and the user interface, and you will discover many differences while using XWiki.

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 users to have 2 hierarchies: the Space/Page hierarchy and the Parent/Child hierarchy.

Managed dependencies Extension Manager now support the concept of managed dependencies. It's pretty much the same thing that the in Maven.

. === Managed dependencies === Extension Manager now support the concept of managed dependencies. It's pretty much the same thing that the {{code language="xml"}}<dependencyManagement>{{/code}} in Maven.