Merge lp://staging/~bruno-bottacini/report-print-send/7.0-report_webkit_custom_paper_size into lp://staging/~report-print-send-core-editors/report-print-send/7.0

I'm interested in this feature and I'm porting a custom module which hacked this feature in v6.
I'll do my best to make a review here.

First off, some formal comments:
- in.txt and out.pdf should probably be left out
- README is empty, either remove it or write something in it please
- please add a copyright note at the top of your files, I think they're useful to avoid ambiguity
- in __openerp__.py:
    - please add a description
    - you may remove the fields init_xml, demo_xml, test, auto_install, complexity and installable
    - there's a space at the end of the "name" field
- it would be nice to get closer to PEP8 (no spaces before ':', 80 cols, empty lines...)
I'll examine and test the module further.

So this a modularization of something that is much easier to do as a patch to the core addons...
Have you been proposing your initial patch for the official addons trunk yet? If not, I humbly suggest you do (I'll review your proposal there too).

Please ignore my comment about PEP8 for the copied/pasted part of the module.
However you need to update your copy of generate_pdf() because patches have been applied to it upstream.

I've forked a branch with an updated code, and proposed to merge it into your branch: https://code.launchpad.net/~numerigraphe-team/report-print-send/7.0-report_webkit_custom_paper_size/+merge/219656

Wouldn't it be cleaner to add a hook in report_webkit to create the command ?

Yannick yes it would be much cleaner, but the problem is the same as with what was initially proposed: unfortunately it won't be accepted in stable releases.
So for v7 we can only
- either take this "white-box reuse" module
- or refuse it and ask those interested to patch their installation on their own (I for one would not mind doing that).

I also noticed this proposal misses an import statement for osv_memory. Fixed it in Numérigraphe's branch.

This project is now hosted on https://github.com/OCA/report-print-send. Please move your proposal there. This guide may help you https://github.com/OCA/maintainers-tools/wiki/How-to-move-a-Merge-Proposal-to-GitHub

Before someone moves this branch to github, can you please give your opinion regarding the modularity first?
This is a case of something that is done very cleanly as a path to the core, but can't ship with OCB, and is hackish as a module.
For my own deployment I decided to use the "patch" approach that I'll maintain for my own needs.
Maybe we should just encourage those interested to do the same, and insist on pushing this to odoo's master branch?