Skip to Content
Last modified by Ecaterina Moraru (Valica) on 2020/01/28 14:36
From version 8.1
Change comment: $escapetool.xml($targetDoc.comment)
To version 9.1
edited by ThibautCamberlin
on 2011/01/28 09:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Application Within Minutes
Parent
... ... @@ -1,0 +1,1 @@
1 +Design.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.XWikiGuest
1 +xwiki:XWiki.ThibautCamberlin
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Syntax
... ... @@ -1,1 +1,1 @@
1 -XWiki 2.1
1 +XWiki 2.0
Content
... ... @@ -1,0 +1,115 @@
1 +{{box title="Contents" cssClass="floatinginfobox"}}
2 +{{toc/}}
3 +{{/box}}
4 +
5 +{{include document="XWiki.DesignClassSheet"/}}
6 +
7 +{{info}}
8 +This page aims to define Application Within Minutes application
9 +{{/info}}
10 +
11 += Main Objective =
12 +
13 +This application aims to allow end users use XWiki powerful structured data management to make collaborative web applications
14 +
15 +== Items to Implement / Improve ==
16 +
17 +* Enpower end user to create XWiki applications and solve XWiki developer issues by:
18 +** Expose the application and create a wizard like mechanism
19 +** Easy structured data creation (class wizard)
20 +** CRUD
21 +*** Create: Automatic form creation (no need to indicate page name, unique id generation)
22 +*** Read: Spreadsheet-like view: automatic livetable, Sheets activated automatically
23 +*** Delete : delete button available from livetable (bulk delete?)
24 +*** Update : inline edition and merging of structured and unstructured data
25 +** Metadata management (create, delete, update, list) and easy administration
26 +** Easy to use
27 +*** Contextual help (tooltips) when creating the app.
28 +*** Polished and shiny
29 +*** More pickers
30 +**** Auto-suggest
31 +**** Advanced auto-suggest (on a class instead of simple key/value datasource)
32 +**** Be able to choose local or global users (global users is not possible AFAIK)
33 +** Advanced editing of sheets
34 +*** Default sheets should be provided for create/edit/view
35 +*** Sheets should be editable and customized
36 +
37 +== More Explanations ==
38 +
39 +=== Expose the application ===
40 +
41 +One important thing is to have the application well exposed in the wiki. This means:
42 +
43 +* Find the right location of the link to it (Add menu, inside the home page)
44 +* Its location: in a dedicated space
45 +* Maybe use a wizard mechanism when creating applications
46 +* and finally make sure that work has been done usability / design side.
47 +
48 +=== Easy Structured data creation ===
49 +
50 +Current class wizard is very helpful for creating XWiki classes. Slight modifications could be added, like page sheet setting in an advanced section, but nothing clearly identified at the moment. The one thing is that class wizard should be integrated into application within minutes pages.
51 +
52 +=== CRUD ===
53 +
54 +==== Create ====
55 +
56 +**Item page name**: Once data structure has been defined, we will want to be able to create items (understand XWiki objects). In the context of an application, it does not always make sense to fill in a page name and then access creation form. Therefore, page title should not be needed and only a "Create" button should link to creation form.
57 +
58 +**unique id generation**: In many cases you want to be able to have a number automatically generated. Similarly to what we do in excel where line number identifies an entry, or what you have in a database with auto-increment. From a user point of view, the suggestion is to have a new entry in the type of data for properties (available in class wizard) that says "auto-increment". (We could think of custom auto-increment that can be configured somewhere else allowing with a specific computation algorithm but this goes beyong current need.) It should also be possible to have page name using page title (or another pattern like a static key) and / or a combination of page title plus a counter.
59 +
60 +**Space**: One space should be created per application. All pages created using this application would be located in that space. Home page of the space would be the home page of the application.
61 +
62 +**Redirect to home page**: When it makes sense for a wiki page to display it when saved, it is not the case for applications. When creating an entry, default behaviour would be to redirect user to application home page (or any otherpage if possible) with a message ([[success message>>http://jira.xwiki.org/jira/browse/XE-723]]?)
63 +
64 +==== Read ====
65 +
66 +**Page sheet detection**: Users should not have to create page sheet, it should be done automatically. Page sheet could be pre-filled in a property of the class when using class wizard. (An improvement could be to have an advanced section in class wizard with ability to change page sheet.)
67 +
68 +**Automatic livetable generation**: When creating the application, users will be able to select what fields they want to be displayed on the home page. That information will be stored and used to automatically generate a livetable on application home page.
69 +
70 +**Home page editing**: There is a need for people to be able to add some "Welcome message" on the home page of the application, above the livetable. Home page of the application should allow this. One solution could be that editing the home page would allow users to edit the content of the wiki page only. When the page is being viewed, some object (maybe the one that will hold livetable configuration) indicates that once we have displayed "Welcome message" (page content) then we have to render livetable. We want people to be able to edit content, we don't want them to be able to edit (livetable) velocity code.
71 +
72 +[[image:EventsExtra-WaterWiki-MozillaFirefox.jpg||style="width: 631px; height: 255px;"]]
73 +
74 +==== Delete ====
75 +
76 +Deleting could take place in two different locations
77 +
78 +**From the home page**: using livetable actions column. Deleting an entry would keep user on the home page of the application.
79 +
80 +**From the page**: XWiki standard feature.
81 +
82 +==== Update ====
83 +
84 +When editing a page that has structured data, it makes no sense to be able to edit page content (unstructured) and structured data in different mode. We should have one mode: inline mode. When editing the page, the wiki should check what type of page we are editing (what object it contains) and trigger inline editing using the right object sheet.
85 +
86 +Note: in the case where we have several objects, it raises the question "What sheet to choose if we have several objects" ? Currently we can discard tag objects and make the asumption that we only have one object per page.
87 +
88 +=== Metadata Management ===
89 +
90 +We should be able to administer application metadata. That administration could be added in space administration section. That administration should enable user to add, delete, update and list metadatas from all properties that have been defined as lists.
91 +
92 +=== Easy to Use ===
93 +
94 +One of the major improvements that could be implemented regarding ease of use and user experience is auto-suggest for simple and multiple select items.
95 +
96 +Here is an example of multiple select property named **addstakeholders** :
97 +
98 +[[image:ApplicationsWithinMinutesRoadmap.ApplicationsWithinMinutes-XWiki-MozillaFirefox2.jpg]]
99 +
100 +**Show In Progress Status:** On some action, like auto-suggest or when creating a page, we could add a loading image similar to this http://ajaxload.info/. This is not specific this application though.
101 +
102 +**Listing applications**: To be able to find easily applications, we could have an application directory (is this managed by extension manager?)
103 +
104 +== Possible Improvements ==
105 +
106 +* Auto-suggest search (à la jira)
107 +* Be able to instanciate an application created (eg 1/ you set a different key which allows you to create new entries based on the same code. Eg 2/ You copy an app to be keep the structure and adapt it to another company departement)
108 +* Excel export feature : XWIKI-5458 (patch) and XE-184
109 +* Advanced editing of sheets
110 +
111 +== Mockups ==
112 +
113 +A mockup for "Document Type Manager" was done: [[Mockups.DocumentTypeManager>>http://incubator.myxwiki.org/xwiki/bin/view/Mockups/DocumentTypeManager]]
114 +
115 +
XWiki.DesignClass[0]
Lead
... ... @@ -1,0 +1,1 @@
1 +Thibaut Camberlin
Status
... ... @@ -1,0 +1,1 @@
1 +Active

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected