Search: concept

Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object

Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?

Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object

Editing Pages XWiki Syntax Understanding XWiki Basic Concepts Document Lifecycle URL resolution Advanced Usage That is what the second generation wiki means :) Programming in the wiki remark: the name "Developer Guide" is confusing, because the first impression is, it's about developing of the XWiki platform Code Zone User Cookbook Administration Installation Common Configuration Skins Changing Color Theme with default skin Encoding Logging Access Rights User Management Group Management Authentication (LDAP, Database...)

xpage=print]] = Understanding XWiki = * [[Basic Concepts >> http://enterprise.xwiki.org/xwiki/bin/view/GettingStarted/XWikiEnterpriseBasicConcepts]] * [[Document Lifecycle >> http://platform.xwiki.org/xwiki/bin/view/Features/DocumentLifecycle]] * [[URL resolution >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/URL+resolution]] = Advanced Usage = That is what the [[second generation wiki>>platform:Main.SecondGenerationWiki]] means :) * [[Programming in the wiki >> http://platform.xwiki.org/xwiki/bin/view/DevGuide/]] //remark: the name "Developer Guide" is confusing, because the first impression is, it's about developing of the XWiki platform// * [[Code Zone >> http://code.xwiki.org/xwiki/bin/view/Main/]] * [[User Cookbook >> Drafts.XEDocUserCookbook]] = Administration = * [[Installation >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation]] * [[Common Configuration >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration]] ** [[Skins>>platform:AdminGuide.Skins]] ** [[Changing Color Theme with default skin >>http://code.xwiki.org/xwiki/bin/view/Skins/ColibriSkin]] ** [[Encoding>>platform:AdminGuide.Encoding]] ** [[Logging >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Logging]] * [[Access Rights >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights]] ** [[User Management >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/User+Management]] ** [[Group Management>>platform:AdminGuide.Group Management]] ** [[Authentication (LDAP, Database...) >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication]] * [[Backup/Restore >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Backup]] ** [[Import/Export pages >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ImportExport]] * [[Security tuning >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Security]] * [[Performance tuning >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Security]] * [[Virtual Wikis >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization]] * [[Clustering >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Clustering]] * [[Administrator Cookbook >> Drafts.XEDocAdminCookbook]] = Further information = * [[User mailing list >>Community.MailingLists]] * [[JIRA (planned features, reported bugs, workarounds) >> https://jira.xwiki.org/secure/Dashboard.jspa]] {{warning}} You shouldn't write your questions as comments to the documentation pages, because in this way these will remain unanswered!

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

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.

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

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

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

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

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

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).