Search: concept

Last modified by Vincent Massol on 2014/10/21

Results 1 - 7 of 7 Page 1

Semantic Tagging Application

Located in
Last modified by Thomas Mortagne on 2024/07/15
Objects
This is an extension to the default tagging mechanism for the XWiki platform which does not link the user-defined tags to a concept. A semantic tag will preserve the default behavior for XWiki in view mode: add icon, remove icon and link to the list of documents which were tagged with it, but will also have semantic information attached.
Attachment content
important; float: left; } .tag-wrapper { /* border: 1px solid $theme.borderColor;*/ } input.button:hover { background-color: transparent; } .tag-add-form #suggested-tag-list, .tag-add-form .tagCloud { list-style-type: none; margin-left:0; text-align: justify; } .tag-add-form #suggested-tag-list li, .tag-add-form .tagCloud li { display:inline-block; padding:0 1em; } .tag-add a.suggested-tag, .tag-add a.suggested-tag:visited { font-size: 100%; } #powered-by, #more-at { float:right; font-size: 80%; } #powered-by img, #more-at img{ width: 10em; height: 3.5em; vertical-align: bottom; } #more-at img{ width: 8em; height: 5em; } .tag-add a.selected-tag, .tag-add a.selected-tag:visited { color: #ccc; } .tag-concept-link { padding: 0.5em 2em 0.5em 0; background: url($xwiki.getSkinFile("icons/silk/link_go.gif")) no-repeat center right; vertical-align: middle; } Style for the tabs 1 always XWiki.TagClass 0 input 1 tags 1 Tags 1 ,| 30 0 com.xpn.xwiki.objects.classes.StaticListClass SemTags.CreateTagForm 0 XWiki.TagClass 1fed1de2-e13c-4230-b4e9-6bbeeebf7eda {{velocity}} #** * Macro to generate the tabs menu. *# #macro(tabber_header $tabberid $header_list) #set($headerno = 1) <ol id="tabber-header"> #foreach($header in $header_list) <li id="header-tab${headerno}" #if((!

Creating a FAQ Application (Manual)

Last modified by Simon Urli on 2023/10/10
Rendered document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: Go to FAQ.WebHome Below the "Add a new question" header, enter a question (which will also be used as the document title) in the Document field Click Create this FAQ You can then enter your question in longer form using the Question field on the template, like this: Click Save & View and then you will see the newly created document, like this: Go back to the FAQ.WebHome page (you can use the breadcrumbs) to see the list of existing questions Conclusion This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.
Raw document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: * Go to ##FAQ.WebHome## * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field * Click //Create this FAQ// * You can then enter your question in longer form using the //Question// field on the template, like this:((( {{image reference="FAQSheetEdit.PNG"/}} ))) * Click //Save & View// and then you will see the newly created document, like this:((( {{image reference="FAQSheetView.PNG"/}} ))) * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions((( {{image reference="FAQsWithEntry.png"/}} ))) = Conclusion = This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.

Creating a FAQ Application (Manual)

Located in
Last modified by Michael Hamann on 2021/10/18
Rendered document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: Go to FAQ.WebHome Below the "Add a new question" header, enter a question (which will also be used as the document title) in the Document field Click Create this FAQ You can then enter your question in longer form using the Question field on the template, like this: Click Save & View and then you will see the newly created document, like this: Go back to the FAQ.WebHome page (you can use the breadcrumbs) to see the list of existing questions Conclusion This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.
Raw document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: * Go to ##FAQ.WebHome## * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field * Click //Create this FAQ// * You can then enter your question in longer form using the //Question// field on the template, like this:((( {{image reference="FAQSheetEdit.PNG"/}} ))) * Click //Save & View// and then you will see the newly created document, like this:((( {{image reference="FAQSheetView.PNG"/}} ))) * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions((( {{image reference="FAQsWithEntry.png"/}} ))) = Conclusion = This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.

References Application

Located in
Last modified by Thomas Mortagne on 2024/07/15
Objects
The best way to grasp the concept is to see how it works on the [[References Page>>xwiki:References.WebHome]] (Code View available [[here>>xwiki:References.WebHome||queryString="viewer=code"]]). == How to use == {{html clean="false" wiki="true"}} All you have to do is to [[download the XAR>>attach:references-1.0.xar]] and [[import>>xwiki:Documentation.AdminGuide.ImportExport]] it in your XWiki.

XWiki At Octo IT University Conference

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
Objects
Vincent and Guillaume presented the {attach:"Wiki 2.0 Talk"|file=XWiki-OCTO-USI-1.2.ppt} which explained the concept of Wiki 2.0 (a.k.a Structured Wikis or Application Wikis or Second Generation Wikis), with XWiki as example.

REST API

Last modified by Marius Dumitru Florea on 2025/02/07
Rendered document content
Understanding resources and representations "An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., an URI in HTTP).
/jobstatus/{jobId} Request parameters: Name Required Values Default Description Version request no true|false false Return also the job request 9.1RC1 progress no true|false true Return also the job progress 9.1RC1 log no true|false false Return also the job log 9.1RC1 log_fromLevel no error|warn|info|debug|trace Indicate the level from which to return logs 9.1RC1 HTTP Method: GET Media types: application/xml (JobStatus element) Description: status of a job Status codes: 200: If the request was successful. 404: If the job status has not been found /joblog/{jobId} Request parameters: Name Required Values Default Description Version level no error|warn|info|debug|trace Indicate the exact level for which to return logs 7.2M3 fromLevel no error|warn|info|debug|trace Indicate the level from which to return logs 7.2M3 HTTP Method: GET Media types: application/xml (JobLog element) Description: log of a job Status codes: 200: If the request was successful. 404: If the job status has not been found /jobs Request parameters: Name Required Values Default Description Version jobType yes The type of the job to pass to the Job Executor 9.1RC1 async no true|false true If false, return the response only when the job is done 9.1RC1 This API is designed to be a REST clone of the JobExecutor Java API (the only real difference right now being way to deal with asynchronous jobs) documented on http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request) are the same and the exact information to put in the job request depends on the job you want to run and are usually documented in the extension this job is coming from (extension module, refactoring, etc.).
Raw document content
= Understanding resources and representations = "An important concept in REST is the existence of resources (sources of specific information), each of which is referenced with a global identifier (e.g., an URI in HTTP).
(eg: ##refactoring/delete/11451##). === /jobstatus/{jobId} {{info}}Since 7.2M3{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##request##|no|##true~|false##|##false##|Return also the job request|9.1RC1 |##progress##|no|##true~|false##|##true##|Return also the job progress|9.1RC1 |##log##|no|##true~|false##|##false##|Return also the job log|9.1RC1 |##log_fromLevel##|no|##error~|warn~|info~|debug~|trace##| |Indicate the level from which to return logs|9.1RC1 * **HTTP Method:** GET ** **Media types:** *** application/xml (JobStatus element) ** **Description:** status of a job ** **Status codes:** *** 200: If the request was successful. *** 404: If the job status has not been found === /joblog/{jobId} {{info}}Since 7.2M3{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##level##|no|##error~|warn~|info~|debug~|trace##| |Indicate the exact level for which to return logs|7.2M3 |##fromLevel##|no|##error~|warn~|info~|debug~|trace##| |Indicate the level from which to return logs|7.2M3 * **HTTP Method:** GET ** **Media types:** *** application/xml (JobLog element) ** **Description:** log of a job ** **Status codes:** *** 200: If the request was successful. *** 404: If the job status has not been found === /jobs {{info}}Since 9.1RC1{{/info}} === Request parameters: |=Name|=Required|=Values|=Default|=Description|=Version |##jobType##|yes| | |The type of the job to pass to the Job Executor|9.1RC1 |##async##|no|##true~|false##|##true##|If false, return the response only when the job is done|9.1RC1 This API is designed to be a REST clone of the JobExecutor Java API (the only real difference right now being way to deal with asynchronous jobs) documented on http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request) are the same and the exact information to put in the job request depends on the job you want to run and are usually documented in the extension this job is coming from (extension module, refactoring, etc

Video Macro

Located in
Last modified by Josué Tille on 2024/11/04
Objects
See the [[Model>>path:http://extensions.xwiki.org/xwiki/bin/view/Extension/Model%20Module]] module to understand the concept of references. Available since XWiki 3.4M1.
Page 1
RSS feed for search on [concept]

Get Connected