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
Creation date
Object type
-
Proposal
77
-
Comments
23
-
Tag
17
-
Style Sheet Extension
5
-
Diagram
2
File type
Upload date
Annotation Feature
Located in
- Rendered document content
Solution n°1 : Richer HTML (not used) This concept is to replace (in a lazy way) initial HTML by a richer HTML.
…So, a new strategy, based on targeting content instead of documents is described by the following: a way to provide a reference to a field in an object in a document will be devised (for example, expanding the DocumentName concept) Annotation model changes to store such a reference to a field (or to the document itself in which case it means 'document content') annotation API changes as follows: where the renderAnnotatedContent can be replaced, in case of a HTML only based approach (as in the above solution), by a or syntax could default to XHTML, etc. on the client, when using the annotations one would need to mark the source (object field, document content, etc) of a piece of XHTML and the fact that it can be annotated.
- Raw document content
=== ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML by a richer HTML.
…So, a new strategy, based on targeting content instead of documents is described by the following: * a way to provide a reference to a field in an object in a document will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store such a reference to a field (or to the document itself in which case it means 'document content') * annotation API changes as follows: {{code}}void addAnnotation(String reference, Annotation ann) String renderAnnotatedContent(String reference, Set<Annotation>, String syntax) Set<Annotation> getAnnotations(String reference){{/code}} where the renderAnnotatedContent can be replaced, in case of a HTML only based approach (as in the above solution), by a {{code}}String getAnnotatedHTML(String reference, Set<Annotation> annotations){{/code}} or syntax could default to XHTML, etc
App Within Minutes Current Issues + Revamp
Located in
- Rendered document content
Static List implies understanding the concept of static and dynamic and also the difference between this field and Database List.
…Next step and Previous step buttons have chevrons that indicate visually the direction in which the process is moving Step 1 Ideas Frame Come back on the mockup and change application into collection 1. We explain the concept of collection and records to the user and guide him through the process: Your data is stored as individual records in a collection. let's define this collection. 2.
- Raw document content
//Static List// implies understanding the concept of static and dynamic and also the difference between this field and Database List. 1*.
…Next step and Previous step buttons have chevrons that indicate visually the direction in which the process is moving )))|(% style="width:590px" %)[[image:AWM- Step1.png]] == **Step 1** == |(% style="width:578px" %)**Ideas**|(% style="width:582px" %)**Frame** |(% style="vertical-align:middle; width:578px" %)((( **__Come back on the mockup and change application into collection__** ~1. We explain the concept of collection and records to the user and guide him through the process: //Your data is stored as individual records in a collection. let's define this collection.// //2.
Application Descriptor
Located in
- Rendered document content
This brainstorming wants to tackle again this concept but a bit different. The differences are that: since the first definition of the descriptor things have changed and now we have many more automated ways to extract information instead of declaring it (example: Extension Manager can extract the version, name, description, dependencies, author, license from the pom; Translations can be automatically bundled, etc.).
…Applications are becoming a major concept inside XWiki and needs to be defined accordingly.
- Raw document content
This brainstorming wants to tackle again this concept but a bit different. The differences are that: * since the first definition of the descriptor things have changed and now we have many more automated ways to extract information instead of declaring it (example: [[Extension>>https://github.com/xwiki/xwiki-commons/blob/master/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-api/src/main/java/org/xwiki/extension/Extension.java]] Manager can extract the version, name, description, dependencies, author, license from the pom; Translations can be automatically bundled, etc.).
…Applications are becoming a major concept inside XWiki and needs to be defined accordingly.
Application Independence
Located in
- Rendered document content
Related Proposals Color Theme Feature for Flamingo Problems XWiki is focused more and more on the concept of applications, but in the same time these applications need to adapt on the skin and version where they are installed.
- Raw document content
== Related Proposals == * [[Color Theme Feature for Flamingo>>Proposal.ColorThemeforFlamingo]] == Problems == XWiki is focused more and more on the concept of applications, but in the same time these applications need to adapt on the skin and version where they are installed.
Architecture 2.0
Located in
- Raw document content
. == Proposal == {{html clean="false" wiki="true"}} * Component-oriented architecture using a Component Manager * Each component group (set of components for implementing a concept) is separated in its own build module and generates a JAR * Make the component 100% independent of the Component Manager used * Register the Component Manager using a Servlet Context Listener * Question: Should we use existing components from the Component Manager implementation?
AWM Actions
Located in
- Rendered document content
Objectives The objective of this proposal is to improve the visual layout and usability of the AWM actions Current Issues These actions currently have the following issues regarding visual layout and usability - Excessive use of vertical space - Component use is not standard with other XWiki controls - Its icons are conflicting on the "delete" actions - The primary Action "Add" is somewhat hidden from the user, taking into account that it is out of alignment with the content area of the page Proposal for changes The changes proposed below are an alternative for the controls based on issues previously mentioned Excessive user of vertical space This can be solved by using the concept of a "toolbar" for these actions. All actions will align horizontally instead of vertically.
- Raw document content
== Objectives == The objective of this proposal is to improve the visual layout and usability of the AWM actions == Current Issues == These actions currently have the following issues regarding visual layout and usability - Excessive use of vertical space - Component use is not standard with other XWiki controls - Its icons are conflicting on the "delete" actions - The primary Action "Add" is somewhat hidden from the user, taking into account that it is out of alignment with the content area of the page [[image:AWMcontext.png]] == Proposal for changes == The changes proposed below are an alternative for the controls based on issues previously mentioned **Excessive user of vertical space** This can be solved by using the concept of a "toolbar" for these actions. All actions will align horizontally instead of vertically.
Benchmark of Knowledge Management apps
Located in
- Rendered document content
Another point of difference between these apps is that Coda has the concept of "Document" and "Pages". While Notion and Outline only have "Pages" Of course, there are other apps in this category, like Anytype, released as a beta in June 2023.
…But if our general UX can be close to these apps, users should have an easier time adapting to Cristal. Some of these concepts are different from XWiki Standard so, if a user comes from there, maybe more time would be necessary to adapt.
- Raw document content
Another point of difference between these apps is that Coda has the concept of "Document" and "Pages". While Notion and Outline only have "Pages" Of course, there are other apps in this category, like Anytype, released as a beta in June 2023.
…But if our general UX can be close to these apps, users should have an easier time adapting to Cristal. Some of these concepts are different from XWiki Standard so, if a user comes from there, maybe more time would be necessary to adapt.
Blog Improvements for XWiki 2.0
Located in
- Attachment content
/xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept doesn't make sense For those who never used it, the publish btn is quiet invisible While creating a blog post, both category AND tags are proposed = > imo not relevant : the 2 processes are contenders CHOSE TAGS or CATEGORIES : not both page : ...
Blog UI Improvement Proposal
Located in
- Attachment content
/xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept doesn't make sense For those who never used it, the publish btn is quiet invisible While creating a blog post, both category AND tags are proposed = > imo not relevant : the 2 processes are contenders CHOSE TAGS or CATEGORIES : not both page : ...
Cache Component
Located in
- Rendered document content
It is generally based on the old cache services concepts even all the names changes but the more I'm working with JBoss cache the more I think this api need some changes as JBoss cache and OSCache has very different way to create there caches.
…I'm thinking of introduce eviction algorithms concept like JBoss or cache4j do to replace the way restriction like capacity and timing are supported.
- Raw document content
It is generally based on the old cache services concepts even all the names changes but the more I'm working with JBoss cache the more I think this api need some changes as JBoss cache and OSCache has very different way to create there caches. === Cache configuration overwriting === Code creating a cache can declare an cache configuration identifier which is used to try to find a configuration in a file for example depends on the cache implementation to overload the default settings cache by cache.
…I'm thinking of introduce eviction algorithms concept like JBoss or cache4j do to replace the way restriction like capacity and timing are supported. == TODO == === Meta cache === for documents cache, Ludovic proposed the idea of something like a "meta cache" when we are using distributed cache: the idea is to only store the documents version in the distributed cache and store the reall document in a local cache.