Refine your search
Select a category and activate filters on the current results
Location
- 100IRC
- 60Proposal
- 13Design
- 9GoogleSummerOfCode
- 7Improvements
- … 10 more
Last author
Creator
Last modification date
Creation date
File type
Uploaded by
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
Interface and Content Language Separation
Located in
- Rendered document content
There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. Interface Language is set from Administration
- Raw document content
There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. * Interface Language ** is set from Administration
Idea: Help by Default
Located in
- Rendered document content
by them For beginner users, the demo applications helps them understand basic XWiki concepts, but after
- Raw document content
helps them understand basic XWiki concepts, but after the initial steps they are still visibile * We
XWiki Forms & URL Mappings
Located in
- Rendered document content
. Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object
- Objects
comment : The combination of *actions* (like <tt>save</tt>) and *request parameters* (like <tt>xredirect</tt>) obviously is a very powerful means to work with XWiki documents. Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?
- Raw document content
", or "1" {table} 1.1 Sample use cases TBD. Example to illustrate formentioned concepts. Ex: Ajax
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
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
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
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
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
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