Search: concept
Last modified by Vincent Massol on 2014/10/21
Refine your search
Select a category and activate filters on the current results
Creator
Last modification date
Creation date
File type
Upload date
Interface Extensions
Located in
- Objects
. * Skin extensions sounds like an afterthought. I wonder if we cannot somehow merge the concepts together
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
Notifications - Watch buttons
Located in
- Rendered document content
that represents those concepts. Using bells not set: followed: blocked: custom: Other proposal using volume I (Simon) find the volume concept interesting for notifications since there's a lot of variability
- Raw document content
for it) - if the page has a partial/custom filter defined Ideally we need icons that represents those concepts
…using volume ==== I (Simon) find the volume concept interesting for notifications since there's a lot
UIX Requirements
Located in
- Objects
if we cannot somehow merge the concepts together. I guess I'd need to see some examples
Mail Archive Application
Located in
- Rendered document content
keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would
- Raw document content
particular keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would
Annotation Feature
Located in
- Rendered document content
) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order
…, expanding the DocumentName concept) Annotation model changes to store such a reference to a field
- Raw document content
? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML
…will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store
XWiki.org Concept (2016)
Located in
- Rendered document content
Improve the layout of XWiki's Concept page. Proposal Before After
- Title
XWiki.org Concept (2016)
- Objects
mails : * [XWiki.org] "XWiki's Concept" page improvements http://markmail.org/message/w3dztiourthzgovo (May 27, 2016)
- Raw document content
* Improve the layout of [[XWiki's Concept>>xwiki:Documentation.UserGuide.Features.SecondGenerationWiki.WebHome]] page. {{toc start="2"/}} (% class="row" %) ((( (% class="col-xs-12 col-sm-12" %) ((( == Proposal == ))) (% class="col-xs-12 col-sm-6 col-md-6" %) ((( Before [[~[~[image:before.png~|~|style
XWiki Patch Service
Located in
- Raw document content
, PatchId toPatch) /** do we need to introduce a concept of dependencies between patches? */ Iterator
Parent-child + Unique ID + Nested Documents
Located in
- Objects
comment : There is not much about the changes in database schema and how to limit extensions broken by the removing of space concept.
…comment : I think this a regression from a user POV. A folder or a nested documents concept seem more intuitive.
Search Interface
Located in
- Rendered document content
not be perceived different than a standard website (the concept of space and wiki should be transparent
- Raw document content
not be perceived different than a standard website (the concept of space and wiki should be transparent
next page »
Page
1
2
3
RSS feed for search on [concept]