Search: concept

Syntaxes to pass. == Best Practices == * ((({{version since="11.3RC1"}}There's now the concept

description : See the [[Configuration API>>Extension.Configuration Module]] for general configuration concepts. == Configuration Permissions == It's possible to implement permission checking for ##ConfigurationSource## properties, to decide who has the rights to view or modify them. To implement this check

summary : Extra Configuration APIs related to platform concepts (e.g. user references)

good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and

="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel

.tag-delete').each(this.ajaxTagDelete); // [semtag] concept list for each tag $$('.doc-tags .tag-list-activator').each(this.ajaxTagConcepts); // [semtag] end concept list for each tag

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

attachment. Changelog 1.5 XWiki 14.0 Add the concept of original metadata document author. 1.4 XWiki

=== //XWiki 14.0// Add the concept of original metadata document author. === 1.4 === //XWiki 12.0

are created (the concept of a saved filter). Follow the same incremental approach for implementing

a completely new Skin. More precisely, through the concepts of UI Extension Points/UI Extension, it allows

using Annotations as explained above. == Namespaces == Component API comes with "namespace" concept

== The XWiki project is older that this component concept and sometimes you can find yourself in code

relate artefacts with one another: * RDF proposes the concept of triples: subject - predicate - object