Search: concept

description : = Users {{info}}Since 12.2{{/info}} Concepts: * This API is independent from where the users are stored (in wiki pages, etc).

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

description : {{info}} You can also check the [[XWiki Platform Developer's Guide>>xwiki:Documentation.DevGuide.Scripting||anchor="HVelocitySpecificInformation"]] for information about Velocity scripting in the XWiki Platform {{/info}} This module offers APIs to evaluate content with Velocity. The following concepts are exposed: * ##VelocityManager##: This is the main entry point for anyone who need to manipulate Velocity scripts * ##VelocityTemplate##: {{version since="15.8"}}This is a helper to manipulate/cache/reuse a "compiled" version of a Velocity script{{/version}} * ##VelocityEngine##: This is the object on which you call ##evaluate()##.

If you simply want to learn how to use the Notifications in XWiki, please look at [[Extension.Notifications Application.WebHome]]. {{/info}} = Concepts = By default, when a user selects an event type to survey, she receives notifications for all events of that event type (except the ones that are anterior to a date configured by that user).

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

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.

:) You will also need programming right to use wiki components and Groovy. The Concept Create a wiki page and transform it into a Wiki Component This Component will only serve as a way to define our Script Service or execute our script.

See the documentation on the [[Script Component>>doc:Extension.Script Component.WebHome]] extension page about how to achieve this. The general concepts explained on this page remain valid, though.

:) You will also need programming right to use wiki components and Groovy. = The Concept = * Create a wiki page and transform it into a Wiki Component * This Component will only serve as a way to define our Script Service or execute our script.

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

Their story began in 2004 in Australia and the concept has been deployed in nearly 10 countries since.