Search: concept

{{success}} **Next: [[XWiki basic concepts>>Documentation.UserGuide.GettingStarted.XWikiBasicConcepts]]** {{/success}}

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

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.

XWiki Classes, Objects, and Properties If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same.

= XWiki Classes, Objects, and Properties = If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same

In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.

If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: Go to FAQ.WebHome Below the "Add a new question" header, enter a question (which will also be used as the document title) in the Document field Click Create this FAQ You can then enter your question in longer form using the Question field on the template, like this: Click Save & View and then you will see the newly created document, like this: Go back to the FAQ.WebHome page (you can use the breadcrumbs) to see the list of existing questions Conclusion This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.

You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.

In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.

If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: * Go to ##FAQ.WebHome## * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field * Click //Create this FAQ// * You can then enter your question in longer form using the //Question// field on the template, like this:((( {{image reference="FAQSheetEdit.PNG"/}} ))) * Click //Save & View// and then you will see the newly created document, like this:((( {{image reference="FAQSheetView.PNG"/}} ))) * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions((( {{image reference="FAQsWithEntry.png"/}} ))) = Conclusion = This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.

You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.

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

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

However, spreadsheets enforce a view of the world that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end-users to perform computational tasks of their choice.

However, spreadsheets enforce a view of the world that consists mostly of tables and numbers rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end-users to perform computational tasks of their choice.

Vincent and Guillaume presented the {attach:"Wiki 2.0 Talk"|file=XWiki-OCTO-USI-1.2.ppt} which explained the concept of Wiki 2.0 (a.k.a Structured Wikis or Application Wikis or Second Generation Wikis), with XWiki as example.

{{image reference="syntaxConversionUnsupported.png"/}} {{id name="HWYSIWYGeditingmode"/}} = Setting the page parent = {{version since="7.2"}} The concept of setting the page parent has been deprecated in favor of the [[Nested Pages feature>>Documentation.UserGuide.Features.ContentOrganization.WebHome]].