openerp-community team mailing list archive

[Nicolas Bessi <nicolas.bessi@xxxxxxxxxxxxxx>]

Hello,

That looks nice.

Simon it would be nice if you can make a little overview on how it works
internally.

I join Joël about security concern, how do you intend to manage security
and allows/prevent user to edit part/all of report content and layout.

Regards

Nicolas


2014-01-27 Simon Lejeune <sle@xxxxxxxxxxx>

> @Guewen (about new line) and @Joel (about font-style and bullets)
> It all depends what you are editing.
> You can see the yellow border around t-field (t-fields are fields of a
> browse record). These t-fields do not behave very well with the edit bar as
> you have (all) seen. The new style tries to apply itself to a t-field, and
> it fails. All the issues related to the edit-bar seem to be linked to this,
> if you are trying to apply style on t-fields (even selected t-fiels inside
> normal text).
>
> About the level of editing, the user has to be either in the group
> 'website designer' (edit all the website, including the reports) or to be
> in the 'website publisher' to explicitely allow him to edit the views of a
> module.
>
> @Romain
> Hello, thanks for your feedback.
> I understand your remark, but the RTE has been designed to *edit* the
> browse record. Maybe this feature will be developped later though.
> But i will display clearly this information, this way the user won't do
> something he doesn't understand.
>
> @Daniel
> Hello, thanks for your feedback.
> Actually, you know on what report you're working so you know what you are
> editing. I'm not sure if it's useful to know which fields on which model
> you're editing, because the goal is a WYSIWYG feature => only the display
> matters. It will be too advanced.
> About additionnal data fields, just go to the html editor and play with
> the t-fields! You will have full control of the report's content there.
> 'Home' and 'end' keys don't work properly, but it's normal. Please try the
> editor!
>
> About the report in a new window, i personally find it nice because it
> allows not to lose the openerp backend. But it can be discussed, if you
> have another idea i willl be happy to hear it.
> Are you okay with loosing your current openerp view when displaying an
> html report ?
>
> And you're pointing something really important with the
> qweb-pdf/qweb-html. It has been decided like that in order to keep the
> logic of one report/one report result and to keep the same logic when
> printing a report.
> Your opinion is important here, do you want a 'print to html' and 'print
> to pdf' button on each document? Will you frequently switch from one type
> to another?
>
> @ Ferdinand
> Yes it is supported, try it !
> Totally agree with you on the benefit and the indispensability of this
> feature.
>
> I strongly encourage you all to use try the online html editor. This is
> the best way to edit the reports. We will improve the way the RTE shows the
> t-field in order to be less buggy when trying to modify a view.
>
> Also, please test some reports. Their codes have all changed and there
> might be some errors.
>
> Thanks again you all for your feedbacks.
> Simon
>
>
> On Mon, Jan 27, 2014 at 4:02 PM, ferdinand <office@xxxxxxxxxx> wrote:
>
>>  On 01/27/2014 11:16 AM, Simon Lejeune wrote:
>>
>> Please correct me if I am wrong -
>> the current (7.0) webkit report engine does not support "repeat column
>> header on page overflow"
>> will this be fixed?
>> for professional reporting this is a must.
>>
>>  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
>>
>>
>>
>
> _______________________________________________
> 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
>
>