Refine your search
Select a category and activate filters on the current results
Wiki
- 27Home
- 11Dev
- 2Extensions Wiki
- 1Rendering
Location
Last author
Creation date
File type
Uploaded by
Upload date
Track: Understand XWiki core concepts
Located in
- Rendered document content
concepts AWM has made it simple to create your first application but it's cheating a bit since it's doing
…the concepts of XClass, XObjects, XProperties, Sheets and Templates. To do that, start by following
- Title
Track: Understand XWiki core concepts
- Raw document content
>>doc:xwiki:Documentation.DevGuide.Tutorials.CreatingExtensions.WebHome]]. = Task 3: Understand XWiki concepts = AWM has made it simple to create your first
…! :) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates
Add concept of image to What's New API
Located in
- Title
Add concept of image to What's New API
- Objects
title : Add concept of image to What's New API
Migration Guide to Nested Pages
Located in
- Rendered document content
retro-compatibility with many existing features and applications we had to keep the concepts of "Page
…the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this: we had some
…, this relationship is crucial. The introduction of the Nested Pages concept In XWiki 7.2, due to frequent users
- Raw document content
the concepts of "Page" and "Space" in XWiki while adapting them to emulate the Nested Pages feature. Here's
…the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this: * we had
…, this relationship is crucial. === The introduction of the Nested Pages concept === In XWiki 7.2, due
Wiki vs Nested Pages
Located in
- Rendered document content
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. Summary There are 2 main use cases when you'd use a Wiki instead of Nested Pages: You want to provide custom Applications
- Raw document content
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. = Summary = There are 2 main use cases when you'd use a Wiki instead of Nested Pages: * You want to provide custom
All Projects
Located in
- Rendered document content
easy to use collaboration solution, organized around the concept of spaces and their applications
- Raw document content
/master/workspaces]]|A powerful yet easy to use collaboration solution, organized around the concept
Content Organization
Located in
- Rendered document content
that Nested Pages are emulated using Nested Spaces. This is why the concept of Nested Spaces still exists
- Raw document content
Nested Spaces. This is why the concept of Nested Spaces still exists. = Migrating to Nested Pages
Selecting a tool for managing Localization
Located in
- Rendered document content
volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english
…translation application. The concept seems to work by application version. We need to verity
- Raw document content
concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation
…on launchpad.net there is a quite extensively developed translation application. The concept seems to work
Summary of the XWiki 7.x Cycle
Located in
- Rendered document content
we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent
- Raw document content
inside other wiki pages. More specifically we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent/Child relationship since it was too complex for end
View Unit Testing
Located in
- Rendered document content
Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: wiki pages (*.xml files) velocity templates (*.vm files) Strategy Specifically the idea is to be able to write integration tests that use the real code except
- Raw document content
{{box cssClass="floatinginfobox" title="**Contents**"}} {{toc/}} {{/box}} = Concept = This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: * wiki pages (##*.xml## files) * velocity templates (##*.vm## files) = Strategy
Architecture
Located in
- Rendered document content
to compile, deploy, etc). General Architecture Architecture Concepts: XWiki is a webapp that is deployed
- Raw document content
actions (no need to compile, deploy, etc). = General Architecture = Architecture Concepts: * XWiki
next page »
Page
1
2
3
4
5
RSS feed for search on [concept]