Search: concept

. (% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; line-height: 19px; " %) [[http:~~/~~/dev.xwiki.org/xwiki/bin/view/Design/ResponsiveSkin>>url:http://dev.xwiki.org/xwiki/bin/view/Design/ResponsiveSkin]] (% style="font-family: sans-serif; font-style: normal; margin-top: 0px; text-align: left; overflow: hidden; " %) ==== (% style="font-size: 23px; line-height: 27px;" %)**Timeline & Milestones**(%%) ==== |=Week|=Days |=Description | 1|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)21 May - 25 May |(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)Design explorations: holistic view (UI wireframe) | 2|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)[28 May - 1 June|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)Design explorations: common widgets/extensions (UI wireframe) (It seemed to be more useful to develop this after the hollistic design has been explored and implemented to be tailored to the final design) **MILESTONE 1 ~-~- Clear concept of what is to be coded/written ** | 3|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)4 June - 8 June|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %) Raw Semantics that work cross platform | 4|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)11 June - 15 June |(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)Desktop implementation (holistic) (css & js) [opera, chrome, safari, ie] | 5|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %)18 June - 22 June|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; line-height: 19px; text-align: left; " %) Desktop implementation (holistic) (css & js) [opera, chrome, safari, ie] (this weeks specifically watered down browser (eg. ie7, ie6?).

| |20 Aug|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left" %)**MILESTONE 5 ~-~- Create distributable version** (% style="font-family: sans-serif; font-style: normal; margin-top: 0px; text-align: left; line-height: 1.2em; overflow: hidden; " %) ==== (% style="font-size: 23px; line-height: 27px; " %)**Deliverables**(%%) ==== |=Milestone |=Description |=Link | 1|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; " %)Clear concept of what is to be coded/written |[[http:~~/~~/sdrv.ms/LZ1iWl>>url:http://sdrv.ms/LZ1iWl]] | 2|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; " %)Codes are written and ready to be implemented into XWiki |[[https:~~/~~/github.com/jssolichin/xorange>>url:https://github.com/jssolichin/xorange]] | 3|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; " %)Codes are implemented, and usable|source: [[https:~~/~~/github.com/jssolichin/xo5>>url:https://github.com/jssolichin/xo5]] [[http:~~/~~/23.21.87.183:8080/xwiki/bin/view/Main/WebHome>>url:http://23.21.87.183:8080/xwiki/bin/view/Main/WebHome]] | 4|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; " %)(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left" %)Chosen features are working and responsive(%%) | search suggest, livetables, blog, color themes, print styling, ie compatibility | 5|(% style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: left; " %)Distributable version created| [[https:~~/~~/github.com/jssolichin/xo5>>url:https://github.com/jssolichin/xo5||style="font-family: sans-serif; font-size: 14px; font-style: normal; text-align: start; "]]; [[http:~~/~~/extensions.xwiki.org/xwiki/bin/view/Extension/xorange>>url:http://extensions.xwiki.org/xwiki/bin/view/Extension/xorange]] (% style="font-family: sans-serif; font-style: normal; margin-top: 0px; text-align: left; line-height: 1.2em; overflow: hidden; " %) ==== (% style="font-size: 19px; line-height: 1.2em; font-size: 19px; line-height: 1.2em; font-size: 23px; line-height: 1.2em" %)**Progess**(%%) ==== |=Time|= Description | May 5| First design exploration.

. ==== 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]]

Analyzing the topics that are covered in different documents of a wiki can help organizing the wiki by, e.g., assigning tags to documents of a topic or grouping documents of a topic in a space (a concept in XWiki that is similar to a directory in a filesystem).

I wonder if we cannot somehow merge the concepts together. I guess I'd need to see some examples for this.

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 Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. Portlet Concepts a portal is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems a portlet is an application that provides a specific piece of content (information or service) to be included as part of a portal page web clients interact with portlets via a request/response paradigm implemented by the portal a portlet container runs portlets and provides them with the required runtime environment manages the life cycle of portlets provides persistent storage for portlet preferences a portlet mode indicates the function a portlet is performing in the render method standard portlet modes are: view, edit and help view: generate markup reflecting the current state of the portlet edit: customize the behavior of the portlet help: provide help information about the portlet a portlet window is the visual component used to display the content generated by a portlet within portal pages a window state is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method possible window states are: normal, maximized and minimized Portlet Life Cycle The life cycle of a portlet is expressed through the init, processAction, render and destroy methods of the Portlet interface.

The Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. == Portlet Concepts == image:portalPageCreation.png * a **portal** is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems * a **portlet** is an application that provides a specific piece of content (information or service) to be included as part of a portal page ** web clients interact with portlets via a request/response paradigm implemented by the portal * a **portlet container** runs portlets and provides them with the required runtime environment ** manages the life cycle of portlets ** provides persistent storage for portlet preferences image:elementsOfAPortalPage.png * a **portlet mode** indicates the function a portlet is performing in the render method ** standard portlet modes are: view, edit and help ** view: generate markup reflecting the current state of the portlet ** edit: customize the behavior of the portlet ** help: provide help information about the portlet * a **portlet window** is the visual component used to display the content generated by a portlet within portal pages * a **window state** is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method ** possible window states are: normal, maximized and minimized == Portlet Life Cycle == The life cycle of a portlet is expressed through the ##init##, ##processAction##, ##render## and ##destroy## methods of the ##Portlet## interface.

profile : * Java proficiency * Familiar with unit testing concepts and best practices * Familiar with functional testing concepts and best practices ** Experience with Selenium and the [[Page Objects>>url:https://code.google.com/p/selenium/wiki/PageObjects]] pattern is preferred * Familiar with web technologies: HTML/CSS/JavaScript * Experience in (unit/functional) testing a previous open source project is a big plus * Willingness to learn and to improve both him/herself and the project