Search: concept

Basics: XWiki's main concepts

Task 3: Understand XWiki concepts AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

:) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates.

Track: Understand XWiki core concepts

= Task 3: Understand XWiki concepts = AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

:) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates.

Add concept of image to What's New API

title : Add concept of image to What's New API

answer : {{info}} The concept of Spaces has been removed from XWiki's UI when Nested Pages were introduced.

summary : "Recommended" concept has been added to Extension and Repository API

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

summary : 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**).

xwiki-semtag-component/documentTags.vm #template("xwikivars.vm") #set($tagsId = 'xdocTags') #set($tagErrorMessage = '') #set($xredirect = $util.encodeURI($doc.getURL('view', "#${tagsId}"))) ## ## ## #macro(displayTag $tag) #if($tagger) #displaySemanticTag($tag) #else <span class="tag-wrapper"><span class="tag"><a property="ctag:label" href="$xwiki.getURL('Main.Tags', 'view', "do=viewTag&amp;tag=$tag")">$tag</a></span>#if($hasedit)<span class="separator">[</span><a href="$doc.getURL('view', "xpage=documentTags&amp;xaction=delete&amp;tag=${tag}&amp;xredirect=${xredirect}")" class="tag-tool tag-delete" title="$msg.get('core.tags.remove.tooltip')">X</a><span class="separator">]</span>#end</span> #end #end #macro(displaySemanticTag $tag) #set($semTag = $tagger.fetchSemanticDetails($tag)) <span class="tag-wrapper"><span class="tag"><a href="$xwiki.getURL('Main.Tags', 'view', "do=viewTag&amp;tag=$tag")">$tag</a></span>#if($hasedit)<span class="separator">[</span><a class="tag-tool tag-list-activator" href="#"> ▼</a><span class="separator">]</span> <div class="conceptList" style="display:none"> #if($semTag.getSemanticDetails().size() == 0) $msg.get("semtags.nodetails") #end #foreach($detail in $semTag.getSemanticDetails()) <span typeof="ctag:Tag" rel="ctag:means" resource="$detail.getUri()" property="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel()</a></span> <br/> #end #set($dbpediaImg = $xwiki.getDocument("SemTags.CreateTagForm").getAttachmentURL("dbpedialogo.png")) <div id="more-at">Powered by <img src='$dbpediaImg' alt="Dbpedia"/></div> </div> <span class="separator">[</span><a href="$doc.getURL('view', "xpage=documentTags&amp;xaction=delete&amp;tag=${tag}&amp;xredirect=${xredirect}")" class="tag-tool tag-delete" title="$msg.get('core.tags.remove.tooltip')">X</a><span class="separator">]</span>#end</span> #end #macro(removeTag $tag) #if($xwiki.tag) #set($result = $xwiki.tag.removeTagFromDocument($tag, $doc.fullName)) #if($result == 'OK' && "$!

_htmlheader.vm xwiki-semtag-component/tags.js // ===================================== // Drop Down // ===================================== var consolelog = function(l) { if(typeof(console) == 'object' && typeof(console.log) == 'function') console.log(l); } // ====================================== // Ajax tag editing // // Make sure the XWiki 'namespace' exists. if (typeof(XWiki) == 'undefined') { XWiki = new Object(); } // Make sure the viewers 'namespace' exists. if (typeof(XWiki.viewers) == 'undefined') { XWiki.viewers = new Object(); } /** * Tag editing. */ XWiki.viewers.Tags = Class.create({ /** * Initialization: add listeners for all tag actions, to perform them via AJAX */ initialize : function() { // delete tags $$('.doc-tags .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 $$('.doc-tags .tag-add a').each(this.createTagAddForm.bind(this)); if ($$('.doc-tags .tag-add-form').length > 0) { this.ajaxifyForm($$('.doc-tags .tag-add-form')[0]); } }, /** * [semtags] add list of concepts */ ajaxTagConcepts : function (item) { item.observe('mouseover', function(event) { if (event) { event.stop(); } if (!item.disabled) { new Ajax.Request( item.href.replace(/&xredirect=.+$/, "&ajax=1"), { onCreate : function () { // ignore "cascade" clicks item.disabled = true; }, onSuccess : function () { // display the concept list var conceptList = item.next('.conceptList'); //consolelog("conceptList = " + conceptList.innerHTML + " item=" + item); var tagConcepts = new XWiki.Tooltip(item, conceptList.innerHTML, {'class': 'conceptList', mouseFollow: false}); }, onFailure : function (response) { new XWiki.widgets.Notification(response.responseText || 'Server not responding', "error"); }, // 0 is returned for network failures, except on IE where a strange large number (12031) is returned.

It mostly bring bugfixes but it also come with a new rendering Syntax variants concept and new experimental Live Data tools (but not used in XWiki Standard yet) meant to replace the current Live Table implementation one day.

It mostly bring bugfixes but it also come with a new rendering Syntax variants concept and new experimental Live Data tools (but not used in XWiki Standard yet) meant to replace the current Live Table implementation one day

Thxs 09:20 <cjd> has joined #xwiki 09:20 <Ramona> has quit 09:28 <tmortagne> Pbas: you are passing the wrong context 09:28 <tmortagne> contex variable is a ScriptContext and the method expect a XWikiContext 09:28 <tmortagne> so that would be xcontext.context 09:29 <tmortagne> (xcontext binding is a public com.xpn.xwiki.api.Context and the method want the more protected XWikiContext) 09:29 <Pbas> Ok thxs I will give a try (I don't understand very well what is context in doc :-( ) 09:30 <tmortagne> not sure what you means by "context in doc" 09:30 <tmortagne> the method want the XWiki context because it's needed to manipulate the database 09:31 <Pbas> In a lot of method there are "protected XWikiContext context The current context, needed by the underlying protected object" but didn't found an explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains things like current wiki, current user, etc. 09:32 <tmortagne> contextual information 09:32 <cjd> hehe the "context" is an object which follows you through the current http request/response cycle and then is deleted 09:32 <tmortagne> and among other things it's needed when you need to access the XWiki database 09:33 <cjd> I had no idea what it was either when I started with XWiki 09:34 <Pbas> It is an important things to use xwiki api but doc about this missing in my opinion 09:34 <tmortagne> in more public/script oriented APIs it's hidden but its still here 09:35 <tmortagne> API taking this XWikiContext are mostly old things which are replaced when we all the API related to document manipulation is a big jump 09:35 <cjd> Context objects are not only confined to XWiki, it's a design pattern in software dev, irronically this is the only link I can find about it... http://c2.com/cgi/wiki?

Thxs 09:20 <cjd> has joined #xwiki 09:20 <Ramona> has quit 09:28 <tmortagne> Pbas: you are passing the wrong context 09:28 <tmortagne> contex variable is a ScriptContext and the method expect a XWikiContext 09:28 <tmortagne> so that would be xcontext.context 09:29 <tmortagne> (xcontext binding is a public com.xpn.xwiki.api.Context and the method want the more protected XWikiContext) 09:29 <Pbas> Ok thxs I will give a try (I don't understand very well what is context in doc :-( ) 09:30 <tmortagne> not sure what you means by "context in doc" 09:30 <tmortagne> the method want the XWiki context because it's needed to manipulate the database 09:31 <Pbas> In a lot of method there are "protected XWikiContext context The current context, needed by the underlying protected object" but didn't found an explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains things like current wiki, current user, etc. 09:32 <tmortagne> contextual information 09:32 <cjd> hehe the "context" is an object which follows you through the current http request/response cycle and then is deleted 09:32 <tmortagne> and among other things it's needed when you need to access the XWiki database 09:33 <cjd> I had no idea what it was either when I started with XWiki 09:34 <Pbas> It is an important things to use xwiki api but doc about this missing in my opinion 09:34 <tmortagne> in more public/script oriented APIs it's hidden but its still here 09:35 <tmortagne> API taking this XWikiContext are mostly old things which are replaced when we all the API related to document manipulation is a big jump 09:35 <cjd> Context objects are not only confined to XWiki, it's a design pattern in software dev, irronically this is the only link I can find about it... http://c2.com/cgi/wiki?