Search: concept

For now I think I'm going to kick back and do some reading ~-~- what a concept (I'm impatient sometimes). Tom

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages.

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages

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.

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

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.

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

Here is an example of the minimum maven builds one should run to check a small change in xwiki-platform-flamingo-skin-resources: mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-resources -Pquality mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test -Pintegration-tests,docker The changes are related to the concept of panels, so we also build mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed.

Since these 2 projects contain libraries that are independent of the concept of wikis, this makes it very easy for everyone to use them in their own projects.

The changes are related to the concept of panels, so we also build ##mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker## If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed

The introduction of the Nested Pages concept In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces under other spaces. It's the Nested Spaces concept. We suddenly had the ability to create a hierarchy of spaces to organize content.

Indeed, the migrator cannot create nested pages in an old XWiki instance where this concept did not exist! Go to the Extension Manager in your wiki, and install the Nested Pages Migrator Application.

However, in order not to break retro-compatibility with many existing features and applications we had to keep the concepts of "Page" and "Space" in XWiki while adapting them to emulate the Nested Pages feature.

For them, this relationship is crucial. === The introduction of the Nested Pages concept === In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces under other spaces. It's the **Nested Spaces** concept. We suddenly had the ability to create a hierarchy of spaces to organize content.

. == Best Practices == * ((({{version since="11.3RC1"}}There's now the concept of a Syntax Registry and new Syntaxes are expected to register themselves in that registry.

Getting to know XWiki Track 1: Understand XWiki concepts of XClass & XObjects Track 2: Extend your application Track 3: Styling XWiki Start contributing Track 4: Report or find an issue Track 5: Contribute to the core Future tracks to document: Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) Track: Contribute to an existing extension Track: Contribute a new extension Track: Add translations Other resources: Getting started with XWiki for extension developers.

= Getting to know XWiki = * Track 1: [[Understand XWiki concepts of XClass & XObjects>>TrackXObjects]] * Track 2: [[Extend your application>>TrackMacro]] * Track 3: [[Styling XWiki>>TrackStyling]] = Start contributing = * Track 4: [[Report or find an issue>>TrackIssues]] * Track 5: [[Contribute to the core>>TrackCore]] Future tracks to document: * Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) * Track: Contribute to an existing extension * Track: Contribute a new extension * Track: Add translations Other resources: * [[Getting started with XWiki for extension developers>>doc:Drafts.GettingStartedWithXWiki]].

Consider packaging the setup into a full stack all-in-one installer and you would have more people complete a proof of concept they can take to sign off -simple things like the sections option in confluence is very useful to have built into the editor -have a non-dev/non-expert user review documentation for xWiki, for example, setting up templates (https://www.xwiki.org/xwiki/bin/view/Help/Templates/), useful function but when setting it up, the "template to use" field was not obvious that it was just a normal page that can be used as the template, and then you search for xwiki create a template you get the same help page that does not describe what the "template to use" actually is (alternatively you could name that field, "Page to use as template")

Consider packaging the setup into a full stack all-in-one installer and you would have more people complete a proof of concept they can take to sign off -simple things like the sections option in confluence is very useful to have built into the editor -have a non-dev/non-expert user review documentation for xWiki, for example, setting up templates (https://www.xwiki.org/xwiki/bin/view/Help/Templates/), useful function but when setting it up, the "template to use" field was not obvious that it was just a normal page that can be used as the template, and then you search for xwiki create a template you get the same help page that does not describe what the "template to use" actually is (alternatively you could name that field, "Page to use as template") )))