From version < 5.2 >
edited by Guillaume Lerouge
on 2011/09/01 14:00
To version < 6.1
edited by Ecaterina Moraru (Valica)
on 2013/11/06 13:03
<
Change comment: Moved page to design:Design.GenericMacrosforApplications

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.GuillaumeLerouge
1 +xwiki:XWiki.evalica
Syntax
... ... @@ -1,1 +1,1 @@
1 -XWiki 1.0
1 +XWiki 2.1
Content
... ... @@ -1,47 +1,1 @@
1 -#includeInContext("XWiki.DesignClassSheet")
2 -
3 -The aim of this proposal is to list the most common needs for applications in XWiki and offer a set of generic macros that answers them.
4 -
5 -#info("I have put users in a separate category. I think users deserve a special treatment as they are more that content-holding XObjects and are used for a very specific purpose.")
6 -
7 -1.1 What's a XWiki application?
8 -
9 -A XWiki application as defined here is a set of pages that lets users enter content in the wiki using a custom page template. Here are examples of XWiki Applications we built for our customers:
10 -
11 -* An application that manages product sheets
12 -** Each product has its own product page. A product has the following fields: name, pricing, image, description, sales pitch
13 -** Users can create new product sheets and edit existing product sheets
14 -** Users can search for a specific product
15 -* A meeting notes application
16 -** When users go to a meeting, they create a meeting record with the following information: date, participants, topic, discussion content, decisions taken
17 -** Users can create new meeting notes & edit existing meeting records
18 -** Users can search in meeting notes
19 -
20 -In each case, we had to create a custom interface. We need to be able to provide generic interface components to cater for the most common use cases. I've listed the application use cases below.
21 -
22 -1.1 What comes with every application
23 -
24 -1.1.1 No generic answer yet
25 -
26 -* Create a new document with an XObject
27 -** We need a standard creation form
28 -* Display a document with an XObject
29 -* List documents with a given XObject
30 -** Standard way to display documents from a list
31 -** Browse the application's documents
32 -** See [this page for a live example>http://incubator.myxwiki.org/xwiki/bin/view/Grid/UserGrid]
33 -* Edit a document holding an XObject
34 -* Search for documents holding an XObject
35 -
36 -1.1.1 Generic answer available
37 -
38 -* Dialog boxes ("Are you sure you want to delete...")
39 -** Default dialog boxes could be improved
40 -* Display macros (info, error, warning)
41 -** Current macros could be improved, new macros created
42 -* Tag a document
43 -* Delete a document
44 -* Add comment to a document
45 -* Attach file to a document
46 -* Compare 2 versions of a document
47 -** The diff could be improved to be cleaner
1 +{{warning}}Moved to [[design:Design.GenericMacrosforApplications]]{{/warning}}
XWiki.DesignClass[0]
Lead
... ... @@ -1,1 +1,0 @@
1 -Guillaume, Cati, JV
Status
... ... @@ -1,1 +1,0 @@
1 -Active
Title
... ... @@ -1,1 +1,0 @@
1 -Generic Macros for Applications
Lead:
Status:
JIRA:

The aim of this proposal is to list the most common needs for applications in XWiki and offer a set of generic macros that answers them.

I have put users in a separate category. I think users deserve a special treatment as they are more that content-holding XObjects and are used for a very specific purpose.

What's a XWiki application?

A XWiki application as defined here is a set of pages that lets users enter content in the wiki using a custom page template. Here are examples of XWiki Applications we built for our customers:

  • An application that manages product sheets
    • Each product has its own product page. A product has the following fields: name, pricing, image, description, sales pitch
    • Users can create new product sheets and edit existing product sheets
    • Users can search for a specific product
  • A meeting notes application
    • When users go to a meeting, they create a meeting record with the following information: date, participants, topic, discussion content, decisions taken
    • Users can create new meeting notes & edit existing meeting records
    • Users can search in meeting notes

In each case, we had to create a custom interface. We need to be able to provide generic interface components to cater for the most common use cases. I've listed the application use cases below.

What comes with every application

No generic answer yet

  • Create a new document with an XObject
    • We need a standard creation form
  • Display a document with an XObject
  • List documents with a given XObject
  • Edit a document holding an XObject
  • Search for documents holding an XObject

Generic answer available

  • Dialog boxes ("Are you sure you want to delete...")
    • Default dialog boxes could be improved
  • Display macros (info, error, warning)
    • Current macros could be improved, new macros created
  • Tag a document
  • Delete a document
  • Add comment to a document
  • Attach file to a document
  • Compare 2 versions of a document
    • The diff could be improved to be cleaner

Get Connected