This report has always been based on "french layout", where there is first
all expenses on one page and all incomes on next page.

In the "british layout", there is only one sheet, showing income -
expense on the same layout ( as we can see today on
 https://en.wikipedia.org/wiki/Income_statement#Sample_income_statement
)

The idea is that we can configure financial section either with two
hierarchies for expense and income to have the french layout, or put all
the "british layout" hierarchy in income and leave expense empty.

(Just moving code arround to prepare next commit)

( see existing styles in Base_getODSStyleSheet )

Exchange action are meant to import/export a list of documents

https://w3c.github.io/server-timing/#the-server-timing-header-field

 ... this js was already included

In its current implementation ( introduced in  4787eadd ), `variation_category` parameter of Inventory API require movements to be in the `predicate_category` table. The approach is to do a first query to get uids of all movements members of the variation and pass their `uid` to catalog. My guess is that this does not scale well. It also uses deprecated `where_expression` and generates invalid SQL when no movements match.

As far as I know, it is only used in [testInventory](https://lab.nexedi.com/nexedi/erp5/blob/ba541ad46e5c593f94fe1ebe79e99d67aafdecb1/product/ERP5/tests/testInventory.py#L1024). We could also consider dropping it, but keeping compatibility is easy.

This implementation just use `variation_text`.

[Test results](https://nexedi.erp5.net/test_result_module/20170502-1FDBAB66) are OK; there is one functional test failure but it really looks unrelated.

@yusei @vpelletier  @seb @romain do you see problems with this ?

/reviewed-on nexedi/erp5!265

Reuse code of delivery to ensure we can customize which item should be
in item table

This reverts commit 2ef67082

This allow customization, original init script is called by new script.

Performance is still not optimal, but should be better than before. At
least it does not assume that movements will be in predicate table.

- Use cloudooo instead of imagemagick
- Avoid to use (probably lossy) png format

_from_  _to_  ____id____  _______________module____________________  ______________comments_______________
pdf     bmp   pdf_to_bmp  erp5.component.document.TransformPdfToBmp  Previous: pdf-(imagemagick)->png->bmp

* acquire objectValues list method instead of using searchFolder
* acquire tales expression for selection name

this is an issue for layout of six-column grid since 16.667 * 6  > 100

/reviewed-on !279

this commit concern 3 bt5: erp5_officejs, erp5_officejs_ooffice, erp5_officejs_jquery_app

this patch concern 3 bt5: erp5_officejs, erp5_officejs_jquery_app, erp5_officejs_ooffice