Skip to Content

Webkit Report Engine

by
Odoo
v 10.0 Third Party 590
Download for v 10.0 Deploy on Odoo.sh Live Preview
You bought this module and need support? Click here!

This module adds a new Report Engine based on WebKit library (wkhtmltopdf) to support reports designed in HTML + CSS.

The module structure and some code is inspired by the report_openoffice module.

The module allows:

  • HTML report definition
  • Multi header support
  • Multi logo
  • Multi company support
  • HTML and CSS-3 support (In the limit of the actual WebKIT version)
  • JavaScript support
  • Raw HTML debugger
  • Book printing capabilities
  • Margins definition
  • Paper size definition

Multiple headers and logos can be defined per company. CSS style, header and footer body are defined per company.

For a sample report see also the webkit_report_sample module, and this video:
http://files.me.com/nbessi/06n92k.mov

Requirements and Installation:

This module requires the wkhtmltopdf library to render HTML documents as PDF. Version 0.9.9 or later is necessary, and can be found at http://code.google.com/p/wkhtmltopdf/ for Linux, Mac OS X (i386) and Windows (32bits).

After installing the library on the OpenERP Server machine, you may need to set the path to the wkhtmltopdf executable file in a system parameter named webkit_path in Settings -> Customization -> Parameters -> System Parameters

If you are experiencing missing header/footer problems on Linux, be sure to install a 'static' version of the library. The default wkhtmltopdf on Ubuntu is known to have this issue.

TODO:

  • JavaScript support activation deactivation
  • Collated and book format support
  • Zip return for separated PDF
  • Web client WYSIWYG

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.