openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #04945
Re: report_webkit future
-
To:
openerp-community@xxxxxxxxxxxxxxxxxxx
-
From:
Fabien Pinckaers <fp@xxxxxxxxxxx>
-
Date:
Tue, 18 Feb 2014 16:50:40 +0100
-
In-reply-to:
<CANkQ1RDLLpa++asz118+SbvuxFJOwJKAnVEfz06SALx1_Js=Kw@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
More info:
Starting v8, we will stop supporting the report_webkit module and we
will use the QWeb report engine of Simon, that is being merged in trunk
in a few hours/days.
On 02/18/2014 11:53 AM, Niels Huylebroeck wrote:
> Nicolas,
>
> I can't see how you can compare wkhtmltopdf and qweb ?
> Wouldn't it make more sense to compare jinja2 with qweb ?
>
> I can see some benefit in using qweb to generate the underlying html
> since it would allow inheritance for report generation (stacking
> multiple reports on top of the same base templates) and reducing the
> number of templating languages to learn while developing with OpenERP.
> But in the end if you want to print to pdf you will have to either use
> wkhtmltopdf or the browser's own ability to convert html to paginated
> format/layout and save or print the output.
>
> Currently though I'm not sure if qweb is used for generating the screen
> layout when you do a print (preview) from the browser. Most of the
> layout there is defined by the regular model view afaik.
>
> Regards,
> Niels
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
>
--
Fabien Pinckaers
CEO OpenERP
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
Follow ups
References