Search: concept

{{image reference="EM-extensionDescription.png"/}} == Supporters and Support Plans {{version since="16.8.0"}} XWiki extensions now have the concept of supporters and support plans. The goal is to replace the very vague concept of **Recommended** we currently have for a very explicit pledge of organizations and individuals (**Supporters**) to support an extension, and to which extent (**Support Plans**).

. === State Management A state represents all the content of a replicated XWiki. This concept derives from the fact that XWoot and XWiki do not share the same data on an implementation level and, before being able to start to function properly, XWoot needs to have its data initialized.

description : API to gather external news related to XWiki. The following concepts are used: * News Source Type: The type of source of news, in the form of a component hint.

A section can be displayed with different ways according to the concept of displayers (For example : Carousel, Article, image, video, simple text ...etc).

comment : Hi Sidali, Interesting concept :) Some feedback: - ThemesCode space pages should be hidden, same for pages inside Themes space (the generated pages); - Themes should have an entry in the Applications panel, read more at http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HApplicationDesign - Your application pages are orphans, run ##xar:format## on pages to check them for such cases - You have problems with the translations, "xwiki.themes.createTheme" does not find the key (tested for english) - The picker is not working, tested with IE9, Chrome 31 and Firefox 26 - You could have used the icon from the default Silk icon set For me is not clear what exactly this application is supposed to do.

More precisely, through the concepts of UI Extension Points/UI Extension, it allows Skins (and any Extensions) to provide places in the UI to let other Extensions contribute some custom content that will be inserted.

It means that you will no longer find the "space" concept in the UI. Instead, each page has now the ability to have children pages, except if it is marked as "Terminal".

Applications of the discussions application dedicated to end users can be found in: * the [[discussions message stream application>>Extension.Discussions - Message Stream.WebHome]] * the [[ActivityPub Application>>Extension.ActivityPub Application]] {{/warning}} Discussions Macro is built on top of several modules that can be useful when integrating the discussions in a new context: * [[Extension.Discussions Server.WebHome]] * [[Extension.Discussions REST.WebHome]] = Concepts = == Discussion Context == A discussion context represents a context that can be linked to a discussion.

However, since Discussions 2.0 it's possible for the applications which relies on Discussions to configure where to store the different elements, and to dynamically chose the storage location. To do so, two concepts have been put in place: an ###applicationHint### must be used in the various API which defines the ###DiscussionStoreConfiguration### component that should be used.

This extension is a dependency of the bridge one, so it should be enough to install the bridge, this extension will be pulled as a dependency. {{/info}} = Concepts = Similar to the [[authorization API>>Extension.Security Module]], this API uses an abstraction to model the access rights as triples (phrases), that all contain: * a subject - who does the action that the access right is about.

**Note 2:** This API only introduces this layer of abstraction on top of the existing XWiki concepts, there is no new implementation of the rights or of their storage.

In its implementation (see details below), the access rights do endup stored as XWikiRights or XWikiGlobalRights objects, but those concepts are internal details from the pov of this API and should never be a concern of the caller of this API

Initially application design was more ambitious, but due to project time constraints it was "dumbed down", so, it should be considered as a "proof of concept". Due to some design decisions (mainly due to "write on read" for Views counter), with large amount of data performance issues //could// appear.

notes : This is initial Proof of Concept.