Search: concept
Last modified by Vincent Massol on 2014/10/21
Refine your search
Select a category and activate filters on the current results
Location
-
IRC
100
-
Proposal
53
-
Design
12
-
Improvements
7
-
PresentationIdea
4
- … 6 more
Creator
Last modification date
Creation date
Object type
-
IRC Bot Archive
100
-
Proposal
77
-
Comments
24
-
Tag
20
-
Presentation Idea
4
- … 2 more
File type
Upload date
IRC Archive for channel #xwiki on 03 June 2013
Located in
- Rendered document content
log 12:16 <altker1281> I think Foswiki does a bit better job with their 'Breadcrumb' concept. Their
…concept that would help 12:26 <tmortagne> vmassol: I guess the build is not always done in the exact same
…concept as xwiki, no? 12:28 <altker1281> vmassol: Personally, I think it should appear slightly bigger
- Raw document content
log 12:16 <altker1281> I think Foswiki does a bit better job with their 'Breadcrumb' concept. Their
…concept that would help 12:26 <tmortagne> vmassol: I guess the build is not always done in the exact same
…concept as xwiki, no? 12:28 <altker1281> vmassol: Personally, I think it should appear slightly bigger
Nested: Drawer
Located in
- Rendered document content
, where Spaces and Pages are replaced with a single Node (Page) concept. The entities hierarchy
- Raw document content
a Nested Documents use case, where Spaces and Pages are replaced with a single Node (Page) concept
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
Help Desk Data Model
Located in
- Rendered document content
XWiki Help Desk Data Model Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. Issue Title Description Language
- Raw document content
= XWiki Help Desk Data Model = Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. |=Issue |Title
IRC Archive for channel #xwiki on 02 September 2013
Located in
- Rendered document content
something btw 11:48 <vmassol> (good morning) 11:48 <gdelhumeau> hi 11:48 <vmassol> if we replace the concept
- Raw document content
something btw 11:48 <vmassol> (good morning) 11:48 <gdelhumeau> hi 11:48 <vmassol> if we replace the concept
Usability Scenario #4 - Task Analysis
Located in
- Rendered document content
Task 1 Observation Users admitted that they would not read the 'Welcome to your wiki' message Users that read the message better understood the concept "wiki made of pages sorted by space". Still this paragraph doesn't reflect the hierarchy Suggestion Improve the message to add the default multi-wiki
- Raw document content
== Task 1 == (% class="col-xs-12 col-sm-12 col-md-12 col-lg-6 pull-left" %) ((( === Observation === * Users admitted that they would not read the 'Welcome to your wiki' message ** Users that read the message better understood the concept "wiki made of pages sorted by space". Still this paragraph doesn't
IRC Archive for channel #xwiki on 30 June 2014
Located in
- Rendered document content
communication ;) 13:46 <vmassol> tmortagne: ok 13:46 <vmassol> thanks 13:46 <vmassol> too bad that this concept
…if some title is badly displayed 14:05 <vmassol> the alternative is to remove the concept of "works
…tick 14:07 <vmassol> to indicate it "works" iwth XE 6.0.1 14:07 <vmassol> but the concept is fuzzy 14
- Raw document content
communication ;) 13:46 <vmassol> tmortagne: ok 13:46 <vmassol> thanks 13:46 <vmassol> too bad that this concept
…if some title is badly displayed 14:05 <vmassol> the alternative is to remove the concept of "works
…tick 14:07 <vmassol> to indicate it "works" iwth XE 6.0.1 14:07 <vmassol> but the concept is fuzzy 14
Homepage - Proposal1: Keep the current homepage, fix problems
Located in
- Rendered document content
P1: Keep the current home page with some improvements that we have been discussing for a while. a) Improve the welcome message displayed by Main.Welcome to focus on wiki concepts. Maybe on the lines of what we have already discussed in the past This hopefully fixes UC1 b) Fix welcome gadget editing
- Raw document content
P1: Keep the current home page with some improvements that we have been discussing for a while. a) Improve the welcome message displayed by Main.Welcome to focus on wiki concepts. Maybe on the lines of what we have [[already discussed in the past>>http://design.xwiki.org/xwiki/bin/view/Improvements
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
Which XAR entry type for which page
Located in
- Rendered document content
10.3 introduce the concept of XAR entry type which allow to configure the protection and upgrade behavior of some of the standard pages. In 10.3 most of the pages are protected but there is pages for which it's not required or which should have a different upgrade behavior. In 10.3 you get a warning
- Raw document content
10.3 introduce the concept of XAR entry type which allow to configure the protection and upgrade behavior of some of the standard pages. In 10.3 most of the pages are protected but there is pages for which it's not required or which should have a different upgrade behavior. In 10.3 you get a warning