Description

Proposal of functionalities which could be achieved by a livetable 2 :

• The livetable need to allow extensions without breaking its default behaviour
  • The objective is to be able to install extensions in using the EM in order to add feature to the default livetable included in XE.
  • As an example it would be possible to have a livetable on a page, then go in the EM to add an extension to it which would allow excel export from the data displayed by the livetable then going back on the already created livetable without it to be broken. Editing the macro would allow you to see the new available option.
• The livetable filters must filter on the displayed content
  • One of the common issue we had with user column filtering was that we had to enter the user fullname like "xwiki.jcoury" instead of nae and surname like "Jean Coury". It has been an issue for multiple years and this issue shouldn't remain any field type.
• The livetable pagination, numbering and the feature in general must respect the available elements for a user as all XE use.
  • ex: I'm displaying 4 lines representing 4 documents but I have no right to see one of them.
  • 
• Filters needs to be able to work with pickers in allowing to define a picker per column (if not a default one) from all the available according to the field type or not.
  • A date field is used to display a column. A picker allow me to pick a date or an interval of dates as a default. An other available picker would be a list of years (depending on the existing elements in the displayed list) etc...
  • This list of picker would be expendable with others downloaded from EM.
• The livetable must allow a live-edition (as an option).
  • As an admin or a user with the edit rights on the displayed element I would be allowed to edit directly the fields in clicking a button which would be displayed inside the field when hovering with the mouse. Clicking on it would turn the field from a view to an edit mode. The value would be saved when clicking on a validation icon. This save would turn back the field to view mode. Clicking outside of the field would go back to view mode without saving.
• The livetable is easy to organize with multiple class / data sources
  • As an example this would allow to have a livetable with the user informations coming from the user class AND the watchlist details that are present on the same page but in a different object from an other class
• The livetable allow offline usage with filtering (as an option)
  • In XE infos are asked to the server every time in order to have the most accurate informations which is great but do not fit the most used cases. Livetables are not made of tons of entries and could be all loaded into the browser cache. I'm thinking of future phone usage in here.
• The livetable allow to have an image displayed per entry
  • Ex: you're working with AWM to buld  car application including a picture of them. You'll need a quick preview of the product directly from the livetable.
• The livetable allow easily to use a custom display for a column
  • Ex: A column is giving a progress bar depending on a numeric value held in the object.
• The livetable need to allow an excel export (as an option).
  • This feature would export all the data required OR displayed by the livetable without being impacted by how they have been included into it.
• The lvietable would use the newest XWiki syntax technology (XWiki/2.1)