Refine your search
Select a category and activate filters on the current results
Location
- 5Proposal
- 1Design
- 1GoogleSummerOfCode
Creator
Last modification date
Creation date
Results 1 - 7 of 7
Page
1
Nested Documents
Located in
- Rendered document content
is completely unrelated to the actual hierarchy. It creates confusion! Idea: Concept of nodes a.k.a Nested
…the user to create the document `A.B.C.D`. In JCR[1], there is only one concept: the "node". A node can
…the concept in the model) Finally, after these steps are accomplished in 7.2 and polished until the end
- Raw document content
documents, which is completely unrelated to the actual hierarchy. It creates confusion! = Idea: Concept
…concept: the "node". A node can have a content, and a list of child nodes. In XWiki, documents could
…explain to the user that some page can have children and some not? === Future (implement the concept
XWiki Model 2.0
Located in
- Rendered document content
) further introduces the concept of shareable nodes which allows multiple paths of access to a node
…the concept of journaled listeners which can ask the repository to re-play all events after a certain
…. JSR283 hence introduces the (optional) concept of shareable nodes. This allows implementing multiple
- Raw document content
://whiteboardjunkie.wordpress.com/2008/11/24/where-am-i-using-jcr-and-why/] * JSR 283 (JCR 2.0) further introduces the concept
…navigations through content * JSR 283 further introduces the concept of journaled listeners which can ask
…) concept of shareable nodes. This allows implementing multiple URIs for a given model object
Group API
Located in
- Rendered document content
. Some Actor can contain other Actors. Separate Group API: Consider that they are separate concepts
…the properties more finely More future proof than options 1 or 2. Imagine we find some concepts that only exist
- Raw document content
that they are separate concepts and that we have a ##UserReference## and ##GroupReference## and different Resolvers
…the properties more finely * More future proof than options 1 or 2. Imagine we find some concepts that only
Application Descriptor
Located in
- Rendered document content
is considered deprecated. This brainstorming wants to tackle again this concept but a bit different
…in Administration, Profile, Search, etc. Applications are becoming a major concept inside XWiki and needs
- Raw document content
is considered deprecated. This brainstorming wants to tackle again this concept but a bit different
…in Administration, Profile, Search, etc. Applications are becoming a major concept inside XWiki and needs
User API
Located in
- Rendered document content
://forum.xwiki.org/t/replace-concept-of-user-in-new-user-api-and-more/6470 https://forum.xwiki.org/t/user-api
- Raw document content
reference format. = Iteration N = See: * https://forum.xwiki.org/t/replace-concept-of-user-in-new
…; } } {{/code}} {{code language="java"}} /** * Abstracts the concept of User reference. This allows
Chart Wizard
Located in
- Rendered document content
/Extension:Graph/Demo) Have the concept of Chart Templates, i.e. a script that generates the graph macro applied
- Raw document content
the concept of Chart Templates, i.e. a script that generates the graph macro applied with wizard variables
Convert all existing tests to the latest technologies
Located in
- Objects
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
Page
1
RSS feed for search on [concept]