Search: concept

\ See Jira for full list of fixed bugs and new features: Application Manager All Wiki Manager 1.0 Milestone 3 features XAWM-23: Separate wiki and wiki alias concepts. XAWM-26: Add pretty name field to wikis decriptors.

reset=true&&pid=10252&fixfor=10432&sorter/field=priority&sorter/order=ASC] 1.1.1.1 All [Wiki Manager>extensions:Extension.Wiki Manager Application] 1.0 Milestone 3 features * XAWM-23: Separate wiki and wiki alias concepts. * XAWM-26: Add pretty name field to wikis decriptors

Job Logs XWiki has the concept of jobs (e.g. when you install or upgrade an Extension or when you delete pages, they all execute in a job).

. == Job Logs == XWiki has the concept of [[jobs>>extensions:Extension.Job Module.WebHome]] (e.g. when you install or upgrade an Extension or when you delete pages, they all execute in a job).

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

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

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

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

code : .w-sectionbox { font-size: 13px; color: #8c8b7e; background: #efeee9; background-color: #f1f1f1; padding: 20px 15px 5px 15px; margin-bottom: 30px; -moz-border-radius: 4px; -webkit-border-radius: 4px; border-radius: 4px; } .w-sectionbox h4 { color: #8c8b7e; margin-top: 0; margin-bottom: 20px; } .w-sectionbox .w-sectionbox { background: #fff; padding: 10px; margin: -5px -4px 5px -4px; } .concept strong { font-weight: 600; } ul.features-grid { list-style: none; margin: 0; padding: 10px 0 0 0; } .features-grid li { padding-left: 51px; margin-bottom: 14px; position: relative; } .ie7 .features-grid li { zoom: 1; display: inline; } .features-grid li p { font-size: 13px; line-height: 1.3em; width: 94%; } .features-grid li h4 { margin: 0; line-height: 1.5em; } .features-grid li:before, .features-grid .fa { position: absolute; top: 5px; left: 0; font-size: 36px; font-family: 'FontAwesome'; color: #efeee9; }

{{velocity}} $xwiki.ssx.use("Documentation.UserGuide.Features.SecondGenerationWiki.WebHome") #set($docextras=[]) {{/velocity}} {{html wiki="true"}} <div class="row concept"> <div class="col-md-9"> First generation wikis are used to collaborate on content.

</h4> <div class="w-sectionbox"> Chris Anderson introduced the concept of [[Long Tail>>http://en.wikipedia.org/wiki/Long_tail]].

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.

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((!

* Support for both Ingress {{velocity}}[[Ingress>>https://kubernetes.io/docs/concepts/services-networking/ingress/]]{{/velocity}} and {{velocity}}[[Istio>>https://istio.io/]]{{/velocity}}

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.

. ==== Challenges and learnings ==== * Discovering Component architecture of XWiki * Discovering Extension Modle API of XWiki * Discovering concept and architecture of Bintray (which is not just a simple single repository) * Discovering Bintray API ==== Possible improvements ==== * Adding support for other types of repositories available on Bintray ---- === **PyPi** === ==== About extension ==== XWiki has possibility to script on its pages in Python.

It enables XWiki user to download any JS library available in NPM registry and converting it internally to WebJar, made it available for import on front pages. ==== Current state ==== Fully developed extension with functionalities of search, download and installation of packages from NPM Registry. ==== Challenges and learnings ==== * Discovering API of NPM registry * Discovering concept and structure of WebJar * Manipulating archives in different formats (TAR, GZ, ZIP) from Java whilst converting JS packages to WebJars ==== Possible improvements ==== No obvious improvements ---- == **Work progress report** == ---- === Milestones === **Milestone 1 [30 May - 26 June]:** - Creating Extension Repository Connector - Bintray * Getting deeper familiarity with the architecture of Extension Module and it's API for new repository extensions * investigation of Bintray and Artifacotry architecture * investigation of Bintray integration API * development of BintrayExtensionRepository * deployment of an extension * documentation creation **Milestone 2 [27 June - 24 July]:** - Creating Extension Repository Connector - PyPi * investigation of PyPi API * investigation of Java-Python integration (Jython) in context of XWiki system * investigation of Python package types, dependency system, version format * development of PypiExtensionRepository * deployment of an extension * documentation creation **Milestone 3 [24 July - 21 August]:** - Creating Extension Repository Connector - NPM * investigation of NPM architecture * investigation of NPM Registry API * investigation of WebJar concept and package structure * development of NPMExtensionRepository * deployment of an extension * documentation creation === Deliverables === D1 [M1]: [[Extension Repository Connector - Bintray>>doc:extensions:Extension.Extension Repository Connector - Bintray.WebHome]] D2 [M2]: [[Extension Repository Connector - PyPI>>doc:extensions:Extension.Extension Repository Connector - Pypi.WebHome]] D3 [M3]: [[Extension Repository Connector - NPM>>doc:extensions:Extension.Extension Repository Connector - NPM.WebHome]]

. == Namespaces == Component API comes with "namespace" concept. The format of the namespaces is ##<type>:<id>##.

It's instantiated in the ##XWikiServletContextListener## class (in the ##xwiki-platform-container-servlet## module). == Accessing components in legacy code == The XWiki project is older that this component concept and sometimes you can find yourself in code which cannot really inject components, you should ideally try to convert it to the components world.