Search: concept

. 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

and wiki alias concepts. XAWM-26: Add pretty name field to wikis decriptors. XAWM-29: Add users or groups

features * XAWM-23: Separate wiki and wiki alias concepts. * XAWM-26: Add pretty name field to wikis

volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english

translation application. The concept seems to work by application version. We need to verity

concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation

on launchpad.net there is a quite extensively developed translation application. The concept seems to work

the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much

programming, you understand the concept of classes, properties, and objects. The presentation level data model

the concept of Reference for any entity of the model and the parser/serializer associated. For now Wiki, Space

the concept of Reference for any entity of the model and the parser/serializer associated. For now Wiki, Space

manipulations around documents and attachment names. It also introduces the concept of Reference for any entity

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

rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end

that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using

="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

resources and representations "An important concept in REST is the existence of resources (sources

://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

and representations = "An important concept in REST is the existence of resources (sources of specific information

/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

this information). I'm sure that your class concept is really easy to use and useful to do this in an online

for using this class concept but I just see the results. The way of realisation (the codes and steps behind

in using your concept are: How do I assign a document type (class) to a web so that every new document