Results 1 - 10 of 32 next page » Page 1 2 3 4

XWiki.org Concept (2016)

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
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>>platform:Main.SecondGenerationWiki]] 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="border:1px solid #E8E8E8" width

XWiki.Org Improvements (2017)

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
Rendered document content
generic image placeholder - no image provided Platform vs. Standard Flavor? Concepts: 1: XWiki Product
name (ex. "Notification app allows you to ... ") Check Carousel entries Features: Concepts + Bundle Extensions Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed
Raw document content
. Standard Flavor? *** Concepts: **** 1: XWiki Product + several Flavors (+ extensions) **** 2: Generic
. "Notification app allows you to ... ") *** Check Carousel entries ** Features: Concepts + Bundle Extensions ** Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed

XWiki Model 2.0

Located in
Last modified by Vincent Massol on 2020/02/21
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

XWiki Forms & URL Mappings

Located in
Last modified by Philipp Roessler on 2020/01/28
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

Application Descriptor

Located in
Last modified by Vincent Massol on 2020/01/28
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

Nested: Deprecating the notion of space everywhere (not just UI)

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
Rendered document content
but not concentrate on supporting page concept in HQL requests. References New typed EntityReferences We need new
is not to write The New Model™ but just to provide to the already existing APIs an easy Page concept oriented
XWikiPage directly expose methods that are not following page concept or that we would want to behave
Raw document content
and Java components but not concentrate on supporting page concept in HQL requests. == References
to the already existing APIs an easy Page concept oriented access. * new com.xpn.page.XWikiPage class used
methods that are not following page concept or that we would want to behave differently for this name

Idea: Explicit Content Actions

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
Rendered document content
concept since people don't know pages can be edited and they are not invited to do it. Adding text
Raw document content
* Problematic wiki concept since people don't know pages can be edited and they are not invited to do it. Adding

Personal Pages

Located in
Last modified by Clemens Robbenhaar on 2022/06/17
Rendered document content
Even though the concept is not very wiki-oriented, several users have been asking over the years to have the ability to have personal pages (a.k.a private pages or user space), visible to the currently logged user only (by default), acting as a kind of personal sandbox. Requirements UC1: Available
Raw document content
Even though the concept is not very wiki-oriented, several users have been asking over the years to have the ability to have personal pages (a.k.a private pages or user space), visible to the currently logged user only (by default), acting as a kind of personal sandbox. = Requirements = * UC1

CAPTCHA investigation 7.0

Located in
Last modified by Ecaterina Moraru (Valica) on 2020/01/28
Rendered document content
to get past it Proof of concept This is just a demo of how to directly use the NO CAPTCHA reCAPTCHA
Raw document content
" %) ((( ))) == Proof of concept == This is just a demo of how to directly use the NO CAPTCHA reCAPTCHA service inside

Change Request

Located in
Last modified by Simon Urli on 2021/05/31
Rendered document content
The idea is to allow contributions to XWiki by requesting for changes, instead of doing them directly. This workflow changes the paradigm of "anyone can edit the wiki" to "anyone can edit the wiki but someone has to validate the changes". We consider a change request as very close to the concept of Github
Raw document content
The idea is to allow contributions to XWiki by requesting for changes, instead of doing them directly. This workflow changes the paradigm of "anyone can edit the wiki" to "anyone can edit the wiki but someone has to validate the changes". We consider a change request as very close to the concept of Github
next page » Page 1 2 3 4
RSS feed for search on [concept]
Tags:
Created by Admin on 2010/05/03

Get Connected