RCP: X.X, Standardize export mechanism

Core

• create an extension point as org.txm.core.results.exporter with attributes:
  • String resultClass =>TXMResult runtime class name that the exporter support, eg. org.txm.concordance.results.Concordance
  • String outputFormat =>CSV, TXT, etc. (like for the extensions SWT Chart Components and Chart Creator )
  • lazy check the installed contributions for the selected result (resultClass) in the export dialog box and add the output/file formats to combo box
• each core plug-in will define their own exporters (or not)

UI

• create a TXMResultTableEditor
  • mutualise somme code as the viewer, the table creation, the navigation/pagination widget, etc. in __createPartControl()
  • look at the SWTChartsComponentProvider and its view export mechanism and see if it can be ported
  • the table must be exported “as is” (sorted or not, filtered or not, etc.)
    • Note: see how to manage the paginated results export
    • problem here is that some results are sorted or filtered in the result data itself but some others are not modified, only the view is modified. It’s not uniform.
• add an “Export data” and/or “Export view” button?

Old note:

h3. Solution

Add ODS (Calc), XLSX (Excel) and TSV formats to the "data" export commands:
* ODS is easy to produce with odftoolit <https://incubator.apache.org/odftoolkit/mvn-site/0.8-incubating/simple-odf/apidocs/index.html>
* other jars are available for Excel
* TSV can be generated by current code or by another jar

Other FR note:

(from redmine: issue id 2163, created on 2017/04/22 by Sebastien Jacquot)

• Relations:
  • child #1491
  • child #1492
  • child #1162
  • child #198