openerp-community team mailing list archive

[Antony Lesuisse <al@xxxxxxxxxxx>]

Tl;dr

trunk-website-al RTE editor
trunk-qweb-report report conversion
this thread is about the report conversion.

The report editor is NOT a report editor, it's just the standard website rich 
text editor, to actually edit report (adding removing fields) you need to edit 
the qweb template source code (but you can use the HTML Ace editor instead of 
the ir.ui.view textarea).

If you have useful feedback about the dozens of reports we converted, please 
post them here, but if you want to discuss the website RTE editor itself 
please do it in an other thread.

In the future (maybe post v8) we might add t-field edition possible from the 
wysiwyg interface but it's not planned this release.


On 01/27/2014 11:16 AM, Simon Lejeune wrote:
> Hello everyone,
> I'm working on the reporting part of OpenERP and i need your help. I'm now at
> a development phase where mass testing of this feature can be (really)
> appreciable.
>
> Big idea is that the reports are now complete webpages, so they are
> customizable using html code. Inside your html code, you can use a simple
> 'magic' syntax to display fields of a browse record, etc. I encourage you to
> check the sale order report for a speaking sample.
>
> The first thing you'll see when testing the sale order is a pdf result. How
> can you modify it ? by displaying the html version of this report. Two way of
> doing this:
> 1) activate the technical feature and go to settings > reportings > reports >
> search for sale.order and replace report's type from 'qweb-pdf' to 'qweb-html'.
> 2) just edit the url from /report/pdf/report/sale.report_saleorder/7 to
> /report/sale.report_saleorder/7
>
> I think you now get the idea : qweb-pdf is the printed qweb-html.
>
> To customize the pdf result you can set paperformat records in
> settings>technical>reporting>Paper Format and set one by default on your
> company and/or explicitely associate a report to a paper format. You can
> define dpi, margin-top etc on them.
>
> Known issues:
> Header and footer of the resulting pdf: you have to define your header in a
> <reportheader> tag and footer in a <reportfooter> one. But the secund thing to
> define is the margin of your header ; if you put text or image too big to be
> displayed under this margin, then you will have some hidden text or even a
> crash of the pdf engine.
>
> Beware that if you use the internal/external layouts that i have set, there is
> a data-report-margin-top attribute on the html root tag that is prioritized
> over the margin-top set in paperformat. So it is this margin-top that you must
> edit!
>
> Notes:
> - Branch is named 'trunk-qweb-report' and is available at
> http://runbot.openerp.com/.
> today's branch is http://trunk-qweb-report-28555-all.runbot.openerp.com/
> - 'website' module is mandatory to dislay the reports. So, either you use 'all
> addons' when connecting to the branch on runbot or you install 'website'
> module on base-install.
> - It's not possible to directly access the xml code of views (webpages) from
> the reporting > reports menu. If you want to edit it, just use the html view
> of the page. To access the views: technical > user interface > views.
>
> I'm sure you all know that the report engine is a tricky part of any software,
> so please be patient as it's likely to be buggy at start.
> That's also why your help and feedback are appreciated.
>
> Feedbacks can contain:
> - traceback (critic issue)
> - no traceback but the datas shown are wrong (critic issue)
> - ugly reports/ulgy html code
> - ideas to simplify this module
> - wanted new features or comments
>
> Thanks in advance,
> Simon
>
>
>
> _______________________________________________
> 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