openerp-community team mailing list archive

[Simon Lejeune <sle@xxxxxxxxxxx>]

Hello Joel, thanks for your feedback.
You are very right when you say you don't know if what you are editing is
"local" or "global". It is not clear.

All the sale orders (and all the other reports) share the same template.
When you edit the html, you edit the template of all your sale orders.
There is (for the moment) no notion of a particular sale order with a
different template than another one.
The only thing varying between the reports are behind the 'magic' syntax
t-fields, t-esc, etc.

I'm going to have a look on your issues, thanks for pointing out them.

Simon



On Mon, Jan 27, 2014 at 2:41 PM, Joël Grand-Guillaume <
joel.grandguillaume@xxxxxxxxxxxxxx> wrote:

> Hi Simon,
>
>
> First of all, thanks for publishing that before it get out, it's very much
> appreciated :) I found the possibility to edit a report and that it'll
> change the object behind very interesting. The salesman will work on the
> report and the information will be saved in the SO => that's smart !
>
> After a first try on my side, some found bugs:
>
>  * Print a SO as html, edit the line description and make it bold. Save
> and wait for refresh => it return to normal and should keep the formatting.
> The same is valide for all kind of formatting (italic, align :center, ...
>
>  * No possible way to setup bullet point correctly. If I edit a line
> description of a SO and chose the bullet point icon, the bullet point
> appear everywhere on my SO and not just for the selected part.
>
>  A part from those bugs, I see a quite big issue without really knowing
> how to solve it:
>
>  * When I edit a report, I edit both the template and the current SO (e.g.
> SO00007). I don't know which of my modifications will appear on all reports
> and which will only apply on my current editing SO.
>
> That is a problem. Wee need to know which part we're editing : the
> template of all SO, or only this SO ?! In term of right management as well,
> I want my salesman to print good SO for my customer, but I don't want them
> to change my template layout...
>
> I don't know how, but I strongly suggest :
>
>  * to have various level of editing possibility related to the user's
> right: an admin will be able to edit the template where a salesman will
> only edit the current SO
>  * to have a visual way to identify what belong to the template and what
> belong to the current report while editing
>  * If it is not possible, better to ensure all the modification are only
> for the current report to save headache to people ;)
>
> Keep up the good work !
>
>
> Regards,
>
> Joël
>
>
>
>
>
>
> On Mon, Jan 27, 2014 at 11:16 AM, Simon Lejeune <sle@xxxxxxxxxxx> 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
>>
>>
>
>
> --
>
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Joël Grand-Guillaume*
> Division Manager
> Business Solutions
>
> +41 21 619 10 28
> www.camptocamp.com
>
>
>