Re: [Openerp-community] report_webkit future

[Francesco Apruzzese]

Il 19/02/2014 23:09, Marc Pierlot ha scritto:

open erp is bad



[troll]
Open Erp is bad! You're right! But OpenERP is cool!
[/troll]

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Nicola Riolini]

another reason for unsubscribe yourself ;)

Il 19/02/2014 23:09, Marc Pierlot ha scritto:

open erp is bad


2014-02-19 23:07 GMT+01:00 Peter Langenberg 
mailto:peter.langenb...@bubbles-it.be>>:


This is a mailing list, you have to unsubsribe yourself :-)

https://launchpad.net/~openerp-community


Peter


2014-02-19 23:05 GMT+01:00 Marc Pierlot mailto:mpier...@gmail.com>>:

Hello,
I do not want to receive messages from you anymore.
Thak you.


2014-02-19 15:00 GMT+01:00 Antony Lesuisse mailto:a...@openerp.com>>:

Xavier Morel is currently working on the technical
documentation.

The first deliverable will be a "getting started with
openerp developement" tutorial. It will introduce all v8
concepts: controllers, html-views (qweb), models,
backend-views (form,list).

After he will work on the reference documentation,
including the server side qweb reference (this will be
based on js one https://doc.openerp.com/trunk/web/qweb/).


On 02/19/2014 02:00 PM, Ovnicraft wrote:




On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse
mailto:a...@openerp.com>
>> wrote:

Yes i forgot to mention that the new report module
natively support excel
reports (or anything else, png, svg, odt...).

For an excel report you should define a controller
that output the file.
For excel 97 you may use xlwt, for excel 2007 and
above you could use qweb
with the bloated office xml format xlsx


Good news for Qweb but please release documentation
about report engine
everything will be easy for everybody.

Regards,

.

   
@http.route('/mymodule/report/__mymodel_excel97_report1/',



type='http', auth="user")
def export_xls(self,ids):
 workbook = xlwt.Workbook()
 (...)
response = request.make_response(None,
headers=[('Content-Type',
'application/vnd.ms-excel'),
('Content-Disposition', 'attachment;
filename=table.xls;')])
workbook.save(response.stream)
return response

Then you define a 'qweb-pdf' report (yes we need
to rename this into
'controller').

We will add an example in the report module.


On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text
documents? Have you looked for
something like wkhtmltopdf that is capable of
generating a xls, doc,
ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to
ensure the community is on
board with this change.

I really like the qweb report engine. You guys
have done a great job.
We will
start migrating our main report set for the
localization by the end of
March.
Do you have an idea of when will it be merged
in trunk (more or less)?
This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por
favor disculpe la brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr

>
__clearcorp.co.cr


>>

CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267


Cel: +(506) 8351 4484



  

Re: [Openerp-community] report_webkit future

[Peter Langenberg]

This is a mailing list, you have to unsubsribe yourself :-)

https://launchpad.net/~openerp-community

Peter


2014-02-19 23:05 GMT+01:00 Marc Pierlot :

> Hello,
>
> I do not want to receive messages from you anymore.
>
> Thak you.
>
>
> 2014-02-19 15:00 GMT+01:00 Antony Lesuisse :
>
> Xavier Morel is currently working on the technical documentation.
>>
>> The first deliverable will be a "getting started with openerp
>> developement" tutorial. It will introduce all v8 concepts: controllers,
>> html-views (qweb), models, backend-views (form,list).
>>
>> After he will work on the reference documentation, including the server
>> side qweb reference (this will be based on js one
>> https://doc.openerp.com/trunk/web/qweb/).
>>
>>
>> On 02/19/2014 02:00 PM, Ovnicraft wrote:
>>
>>>
>>>
>>>
>>> On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse >> > wrote:
>>>
>>> Yes i forgot to mention that the new report module natively support
>>> excel
>>> reports (or anything else, png, svg, odt...).
>>>
>>> For an excel report you should define a controller that output the
>>> file.
>>> For excel 97 you may use xlwt, for excel 2007 and above you could
>>> use qweb
>>> with the bloated office xml format xlsx
>>>
>>>
>>> Good news for Qweb but please release documentation about report engine
>>> everything will be easy for everybody.
>>>
>>> Regards,
>>>
>>> .
>>>
>>> @http.route('/mymodule/report/__mymodel_excel97_report1/<
>>> str:__ids>',
>>>
>>> type='http', auth="user")
>>> def export_xls(self,ids):
>>>  workbook = xlwt.Workbook()
>>>  (...)
>>> response = request.make_response(None, headers=[('Content-Type',
>>> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
>>> filename=table.xls;')])
>>> workbook.save(response.stream)
>>> return response
>>>
>>> Then you define a 'qweb-pdf' report (yes we need to rename this into
>>> 'controller').
>>>
>>> We will add an example in the report module.
>>>
>>>
>>> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>>>
>>> Antony,
>>>
>>> What about generating spreadsheets or text documents? Have you
>>> looked for
>>> something like wkhtmltopdf that is capable of generating a xls,
>>> doc,
>>> ods or
>>> odt from an html? Is it in your plans?
>>>
>>> This could be, I think, the missing feature to ensure the
>>> community is on
>>> board with this change.
>>>
>>> I really like the qweb report engine. You guys have done a great
>>> job.
>>> We will
>>> start migrating our main report set for the localization by the
>>> end of
>>> March.
>>> Do you have an idea of when will it be merged in trunk (more or
>>> less)?
>>> This
>>> can help to plan our work to prepare for v8.
>>>
>>> Regards,
>>> --
>>> PS: escribí este email desde mi teléfono, por favor disculpe la
>>> brevedad y
>>> cualquier error de escritura.
>>>
>>> Carlos Vásquez
>>> CTO · Director de Ingeniería
>>>
>>> carlos.vasq...@clearcorp.co.cr >> clearcorp.co.cr>
>>>  >>
>>> >
>>>
>>> CR: +(506) 4000 CORP (4000 2677)
>>> US: +1 (786) 472-4267 
>>> Cel: +(506) 8351 4484 
>>>
>>> skype: crvasquez
>>> twitter: cvclearcorp
>>>
>>> 300 m. Este de la Escuela
>>> Calle de Platanares
>>> 11402 San Jerónimo, Moravia
>>> San José, Costa Rica
>>>
>>> http://www.clearcorp.co.cr
>>>
>>>
>>> _
>>> Mailing list: https://launchpad.net/~__openerp-community
>>> 
>>> Post to : openerp-community@lists.__launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~__openerp-community
>>> 
>>> More help   : https://help.launchpad.net/__ListHelp
>>>
>>> 
>>>
>>>
>>>
>>>
>>> --
>>> Cristian Salamea
>>> @ovnicraft
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to : openerp-community@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.la

Re: [Openerp-community] report_webkit future

[Peter Langenberg]

Marc,

Did you forget your pills again ? Take one and go to bed.

Thanx

Peter


2014-02-19 23:09 GMT+01:00 Marc Pierlot :

> open erp is bad
>
>
> 2014-02-19 23:07 GMT+01:00 Peter Langenberg <
> peter.langenb...@bubbles-it.be>:
>
> This is a mailing list, you have to unsubsribe yourself :-)
>>
>> https://launchpad.net/~openerp-community
>>
>> Peter
>>
>>
>> 2014-02-19 23:05 GMT+01:00 Marc Pierlot :
>>
>>> Hello,
>>>
>>> I do not want to receive messages from you anymore.
>>>
>>> Thak you.
>>>
>>>
>>> 2014-02-19 15:00 GMT+01:00 Antony Lesuisse :
>>>
>>> Xavier Morel is currently working on the technical documentation.

 The first deliverable will be a "getting started with openerp
 developement" tutorial. It will introduce all v8 concepts: controllers,
 html-views (qweb), models, backend-views (form,list).

 After he will work on the reference documentation, including the server
 side qweb reference (this will be based on js one
 https://doc.openerp.com/trunk/web/qweb/).


 On 02/19/2014 02:00 PM, Ovnicraft wrote:

>
>
>
> On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse  > wrote:
>
> Yes i forgot to mention that the new report module natively
> support excel
> reports (or anything else, png, svg, odt...).
>
> For an excel report you should define a controller that output the
> file.
> For excel 97 you may use xlwt, for excel 2007 and above you could
> use qweb
> with the bloated office xml format xlsx
>
>
> Good news for Qweb but please release documentation about report engine
> everything will be easy for everybody.
>
> Regards,
>
> .
>
> @http.route('/mymodule/report/__mymodel_excel97_report1/<
> str:__ids>',
>
> type='http', auth="user")
> def export_xls(self,ids):
>  workbook = xlwt.Workbook()
>  (...)
> response = request.make_response(None,
> headers=[('Content-Type',
> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
> filename=table.xls;')])
> workbook.save(response.stream)
> return response
>
> Then you define a 'qweb-pdf' report (yes we need to rename this
> into
> 'controller').
>
> We will add an example in the report module.
>
>
> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>
> Antony,
>
> What about generating spreadsheets or text documents? Have you
> looked for
> something like wkhtmltopdf that is capable of generating a
> xls, doc,
> ods or
> odt from an html? Is it in your plans?
>
> This could be, I think, the missing feature to ensure the
> community is on
> board with this change.
>
> I really like the qweb report engine. You guys have done a
> great job.
> We will
> start migrating our main report set for the localization by
> the end of
> March.
> Do you have an idea of when will it be merged in trunk (more
> or less)?
> This
> can help to plan our work to prepare for v8.
>
> Regards,
> --
> PS: escribí este email desde mi teléfono, por favor disculpe
> la brevedad y
> cualquier error de escritura.
>
> Carlos Vásquez
> CTO · Director de Ingeniería
>
> carlos.vasq...@clearcorp.co.cr  clearcorp.co.cr>
>  
> >
>
> CR: +(506) 4000 CORP (4000 2677)
> US: +1 (786) 472-4267 
> Cel: +(506) 8351 4484 
>
> skype: crvasquez
> twitter: cvclearcorp
>
> 300 m. Este de la Escuela
> Calle de Platanares
> 11402 San Jerónimo, Moravia
> San José, Costa Rica
>
> http://www.clearcorp.co.cr
>
>
> _
> Mailing list: https://launchpad.net/~__openerp-community
> 
> Post to : openerp-community@lists.__launchpad.net
> 
> Unsubscribe : https://launchpad.net/~__openerp-community
> 
> More help   : https://help.launchpad.net/__ListHelp
>
> 
>
>
>
>
> --
> Cristian Salamea
> @ovnicraft
>

 ___
 Mailing list: https://launchpad.net/~openerp-community
 Post to : openerp-community@lists

Re: [Openerp-community] report_webkit future

[Marc Pierlot]

open erp is bad


2014-02-19 23:07 GMT+01:00 Peter Langenberg 
:

> This is a mailing list, you have to unsubsribe yourself :-)
>
> https://launchpad.net/~openerp-community
>
> Peter
>
>
> 2014-02-19 23:05 GMT+01:00 Marc Pierlot :
>
>> Hello,
>>
>> I do not want to receive messages from you anymore.
>>
>> Thak you.
>>
>>
>> 2014-02-19 15:00 GMT+01:00 Antony Lesuisse :
>>
>> Xavier Morel is currently working on the technical documentation.
>>>
>>> The first deliverable will be a "getting started with openerp
>>> developement" tutorial. It will introduce all v8 concepts: controllers,
>>> html-views (qweb), models, backend-views (form,list).
>>>
>>> After he will work on the reference documentation, including the server
>>> side qweb reference (this will be based on js one
>>> https://doc.openerp.com/trunk/web/qweb/).
>>>
>>>
>>> On 02/19/2014 02:00 PM, Ovnicraft wrote:
>>>



 On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse >>> > wrote:

 Yes i forgot to mention that the new report module natively support
 excel
 reports (or anything else, png, svg, odt...).

 For an excel report you should define a controller that output the
 file.
 For excel 97 you may use xlwt, for excel 2007 and above you could
 use qweb
 with the bloated office xml format xlsx


 Good news for Qweb but please release documentation about report engine
 everything will be easy for everybody.

 Regards,

 .

 @http.route('/mymodule/report/__mymodel_excel97_report1/<
 str:__ids>',

 type='http', auth="user")
 def export_xls(self,ids):
  workbook = xlwt.Workbook()
  (...)
 response = request.make_response(None, headers=[('Content-Type',
 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
 filename=table.xls;')])
 workbook.save(response.stream)
 return response

 Then you define a 'qweb-pdf' report (yes we need to rename this into
 'controller').

 We will add an example in the report module.


 On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

 Antony,

 What about generating spreadsheets or text documents? Have you
 looked for
 something like wkhtmltopdf that is capable of generating a xls,
 doc,
 ods or
 odt from an html? Is it in your plans?

 This could be, I think, the missing feature to ensure the
 community is on
 board with this change.

 I really like the qweb report engine. You guys have done a
 great job.
 We will
 start migrating our main report set for the localization by the
 end of
 March.
 Do you have an idea of when will it be merged in trunk (more or
 less)?
 This
 can help to plan our work to prepare for v8.

 Regards,
 --
 PS: escribí este email desde mi teléfono, por favor disculpe la
 brevedad y
 cualquier error de escritura.

 Carlos Vásquez
 CTO · Director de Ingeniería

 carlos.vasq...@clearcorp.co.cr 
  >

 CR: +(506) 4000 CORP (4000 2677)
 US: +1 (786) 472-4267 
 Cel: +(506) 8351 4484 

 skype: crvasquez
 twitter: cvclearcorp

 300 m. Este de la Escuela
 Calle de Platanares
 11402 San Jerónimo, Moravia
 San José, Costa Rica

 http://www.clearcorp.co.cr


 _
 Mailing list: https://launchpad.net/~__openerp-community
 
 Post to : openerp-community@lists.__launchpad.net
 
 Unsubscribe : https://launchpad.net/~__openerp-community
 
 More help   : https://help.launchpad.net/__ListHelp

 




 --
 Cristian Salamea
 @ovnicraft

>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to : openerp-community@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to : openerp-community@lists.launchpad.net
>> Unsubscribe : https://l

Re: [Openerp-community] report_webkit future

[Marc Pierlot]

Hello,

I do not want to receive messages from you anymore.

Thak you.


2014-02-19 15:00 GMT+01:00 Antony Lesuisse :

> Xavier Morel is currently working on the technical documentation.
>
> The first deliverable will be a "getting started with openerp
> developement" tutorial. It will introduce all v8 concepts: controllers,
> html-views (qweb), models, backend-views (form,list).
>
> After he will work on the reference documentation, including the server
> side qweb reference (this will be based on js one
> https://doc.openerp.com/trunk/web/qweb/).
>
>
> On 02/19/2014 02:00 PM, Ovnicraft wrote:
>
>>
>>
>>
>> On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse > > wrote:
>>
>> Yes i forgot to mention that the new report module natively support
>> excel
>> reports (or anything else, png, svg, odt...).
>>
>> For an excel report you should define a controller that output the
>> file.
>> For excel 97 you may use xlwt, for excel 2007 and above you could use
>> qweb
>> with the bloated office xml format xlsx
>>
>>
>> Good news for Qweb but please release documentation about report engine
>> everything will be easy for everybody.
>>
>> Regards,
>>
>> .
>>
>> @http.route('/mymodule/report/__mymodel_excel97_report1/',
>>
>> type='http', auth="user")
>> def export_xls(self,ids):
>>  workbook = xlwt.Workbook()
>>  (...)
>> response = request.make_response(None, headers=[('Content-Type',
>> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
>> filename=table.xls;')])
>> workbook.save(response.stream)
>> return response
>>
>> Then you define a 'qweb-pdf' report (yes we need to rename this into
>> 'controller').
>>
>> We will add an example in the report module.
>>
>>
>> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>>
>> Antony,
>>
>> What about generating spreadsheets or text documents? Have you
>> looked for
>> something like wkhtmltopdf that is capable of generating a xls,
>> doc,
>> ods or
>> odt from an html? Is it in your plans?
>>
>> This could be, I think, the missing feature to ensure the
>> community is on
>> board with this change.
>>
>> I really like the qweb report engine. You guys have done a great
>> job.
>> We will
>> start migrating our main report set for the localization by the
>> end of
>> March.
>> Do you have an idea of when will it be merged in trunk (more or
>> less)?
>> This
>> can help to plan our work to prepare for v8.
>>
>> Regards,
>> --
>> PS: escribí este email desde mi teléfono, por favor disculpe la
>> brevedad y
>> cualquier error de escritura.
>>
>> Carlos Vásquez
>> CTO · Director de Ingeniería
>>
>> carlos.vasq...@clearcorp.co.cr > clearcorp.co.cr>
>> >
>> >
>>
>> CR: +(506) 4000 CORP (4000 2677)
>> US: +1 (786) 472-4267 
>> Cel: +(506) 8351 4484 
>>
>> skype: crvasquez
>> twitter: cvclearcorp
>>
>> 300 m. Este de la Escuela
>> Calle de Platanares
>> 11402 San Jerónimo, Moravia
>> San José, Costa Rica
>>
>> http://www.clearcorp.co.cr
>>
>>
>> _
>> Mailing list: https://launchpad.net/~__openerp-community
>> 
>> Post to : openerp-community@lists.__launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~__openerp-community
>> 
>> More help   : https://help.launchpad.net/__ListHelp
>>
>> 
>>
>>
>>
>>
>> --
>> Cristian Salamea
>> @ovnicraft
>>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Antony Lesuisse]

Xavier Morel is currently working on the technical documentation.

The first deliverable will be a "getting started with openerp developement" 
tutorial. It will introduce all v8 concepts: controllers, html-views (qweb), 
models, backend-views (form,list).


After he will work on the reference documentation, including the server side 
qweb reference (this will be based on js one 
https://doc.openerp.com/trunk/web/qweb/).


On 02/19/2014 02:00 PM, Ovnicraft wrote:




On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse mailto:a...@openerp.com>> wrote:

Yes i forgot to mention that the new report module natively support excel
reports (or anything else, png, svg, odt...).

For an excel report you should define a controller that output the file.
For excel 97 you may use xlwt, for excel 2007 and above you could use qweb
with the bloated office xml format xlsx


Good news for Qweb but please release documentation about report engine
everything will be easy for everybody.

Regards,

.

@http.route('/mymodule/report/__mymodel_excel97_report1/',
type='http', auth="user")
def export_xls(self,ids):
 workbook = xlwt.Workbook()
 (...)
response = request.make_response(None, headers=[('Content-Type',
'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
filename=table.xls;')])
workbook.save(response.stream)
return response

Then you define a 'qweb-pdf' report (yes we need to rename this into
'controller').

We will add an example in the report module.


On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text documents? Have you looked 
for
something like wkhtmltopdf that is capable of generating a xls, doc,
ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the community is 
on
board with this change.

I really like the qweb report engine. You guys have done a great job.
We will
start migrating our main report set for the localization by the end of
March.
Do you have an idea of when will it be merged in trunk (more or less)?
This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe la 
brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr 
>

CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267 
Cel: +(506) 8351 4484 
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr


_
Mailing list: https://launchpad.net/~__openerp-community

Post to : openerp-community@lists.__launchpad.net

Unsubscribe : https://launchpad.net/~__openerp-community

More help   : https://help.launchpad.net/__ListHelp





--
Cristian Salamea
@ovnicraft


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Alexandre Fayolle]

On 19/02/2014 14:29, Antony Lesuisse wrote:
> Yes and no :) , Fabien Meghazi did it a few years ago, before joining
> openerp, the qweb template is awful but it works.
>

Maintainability trumps mere feasibility all the time.

-- 
Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Raphael Valyi]

On Wed, Feb 19, 2014 at 1:47 AM, Ferdinand Gassauer wrote:

>  On 2014-02-19 04:59, Antony Lesuisse wrote:
>
> Thank you for clarifying this.
>
> IMO such information should be part of OpenERP Marketing activities
> towards partners and would avoid mail threads like this one
>
> The argument
> ***
>
> 2/ OpenERP Enterprise covers custom module migration at a price of
> 800 EURO/1000 lines of code. One should check the number of lines of code per
> report but it should be something around 200 EURO to migrate a report, which 
> is
> nothing. So, I don't think it's a blocking point for a migration.
> ***
> is difficult to sell. And *"... which is nothing" *is a miss
> interpretation of the reality of the market - every cent counts. It is
> either the customer or the partner who has to pay and loses money.
> No customer who ordered webkit reports in v6 or v7 is prepared to pay
> extra migration fee during migration to v8.
> But as we learned from Antony it will not be necessary.
>

First of all, thanks to Antony for the comments. So basically it's the
industry standard deprecation cycle I was asking for.

Now, about Fabien comment and Ferdinand answer here:
Fabien, with all my respect, this is exactly what I call crappy marketing.
 Come on, even if you claim it's 200 euros from OpenERP SA per report,
people should consider that:

1) an offshore noob working so cheap he won't be here next year, who has no
clue at all what are the process in the company is never going to migrate
anything customized properly in the first shot.
There will need to be many iterations of tests and specifications from
specialized guys knowing the enterprise processes, ideally the guys who
guys who do the implementation, and no they don't cost 5 USD/hour, so I'm
afraid the total price isn't that low.

2) many customized reports depends on community or customized modules the
offshore noob of the day has no clue about. So what I just told about the
report applies to the extra modules to and just would rise the cost orders
of magnitudes higher than what you told (consider 20 000 lines of
localization you have no idea how it works, these kind of stuff).

3) 200 euros added to the price of OpenERP Enterprise isn't appropriate for
many countries.
That's cool if that's attractive in Switzerland or Luxembourg.

Now I can tell you that in a country like Brazil where I work this is not
attractive. You can tell it's 5x cheaper than SAP, but you know what,
exactly because of that SAP has like zero % marketshare in the SMB's here.
And I don't talk about Bolivia, Peru, African countries etc... We can
marginally sell Enterprises contracts as we do, but bare in mind that
unless you are able to reprice aggressively per territory (and that won't
apply to an offshore work hour anyway), that won't address mass market here.
So it means that with our without your service, many people should be able
to pick OpenERP and build evolution strategies that fit their economical
realities. This is usually this freedom people are looking for when they
look for an open source project.


So, Fabien, this kind of "it's only 200 euros" doesn't match any reality,
it's like the "60 euros localizations" you mention sometimes.
Anybody with more than 1 OpenERP migration experience know that perfectly
and these guys are the opinion leaders sharing their experience to the guys
entering now.
So a good marketing strategy would be not talking to them just as if they
joined yesterday.


Regards.
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Antony Lesuisse]

Yes and no :) , Fabien Meghazi did it a few years ago, before joining openerp, 
the qweb template is awful but it works.


On 02/19/2014 02:17 PM, Alexandre Fayolle wrote:

Hello Anthony. I'll assume you were kidding about writing qweb based
xslx reports.

http://pythonhosted.org/openpyxl/ is a nice python library to handle
these files.

Alexandre

On 19/02/2014 12:49, Antony Lesuisse wrote:

Yes i forgot to mention that the new report module natively support
excel reports (or anything else, png, svg, odt...).

For an excel report you should define a controller that output the
file. For excel 97 you may use xlwt, for excel 2007 and above you
could use qweb with the bloated office xml format xlsx.

@http.route('/mymodule/report/mymodel_excel97_report1/',
type='http', auth="user")
def export_xls(self,ids):
 workbook = xlwt.Workbook()
 (...)
response = request.make_response(None, headers=[('Content-Type',
'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
filename=table.xls;')])
workbook.save(response.stream)
return response

Then you define a 'qweb-pdf' report (yes we need to rename this into
'controller').

We will add an example in the report module.

On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text documents? Have you looked
for
something like wkhtmltopdf that is capable of generating a xls, doc,
ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the community
is on
board with this change.

I really like the qweb report engine. You guys have done a great job.
We will
start migrating our main report set for the localization by the end
of March.
Do you have an idea of when will it be merged in trunk (more or
less)? This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe la
brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr 
CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267
Cel: +(506) 8351 4484
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr



___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Alexandre Fayolle]

Hello Anthony. I'll assume you were kidding about writing qweb based
xslx reports.

http://pythonhosted.org/openpyxl/ is a nice python library to handle
these files.

Alexandre

On 19/02/2014 12:49, Antony Lesuisse wrote:
> Yes i forgot to mention that the new report module natively support
> excel reports (or anything else, png, svg, odt...).
>
> For an excel report you should define a controller that output the
> file. For excel 97 you may use xlwt, for excel 2007 and above you
> could use qweb with the bloated office xml format xlsx.
>
> @http.route('/mymodule/report/mymodel_excel97_report1/',
> type='http', auth="user")
> def export_xls(self,ids):
> workbook = xlwt.Workbook()
> (...)
>response = request.make_response(None, headers=[('Content-Type',
> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
> filename=table.xls;')])
>workbook.save(response.stream)
>return response
>
> Then you define a 'qweb-pdf' report (yes we need to rename this into
> 'controller').
>
> We will add an example in the report module.
>
> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>> Antony,
>>
>> What about generating spreadsheets or text documents? Have you looked
>> for
>> something like wkhtmltopdf that is capable of generating a xls, doc,
>> ods or
>> odt from an html? Is it in your plans?
>>
>> This could be, I think, the missing feature to ensure the community
>> is on
>> board with this change.
>>
>> I really like the qweb report engine. You guys have done a great job.
>> We will
>> start migrating our main report set for the localization by the end
>> of March.
>> Do you have an idea of when will it be merged in trunk (more or
>> less)? This
>> can help to plan our work to prepare for v8.
>>
>> Regards,
>> -- 
>> PS: escribí este email desde mi teléfono, por favor disculpe la
>> brevedad y
>> cualquier error de escritura.
>>
>> Carlos Vásquez
>> CTO · Director de Ingeniería
>>
>> carlos.vasq...@clearcorp.co.cr 
>> CR: +(506) 4000 CORP (4000 2677)
>> US: +1 (786) 472-4267
>> Cel: +(506) 8351 4484
>> skype: crvasquez
>> twitter: cvclearcorp
>>
>> 300 m. Este de la Escuela
>> Calle de Platanares
>> 11402 San Jerónimo, Moravia
>> San José, Costa Rica
>>
>> http://www.clearcorp.co.cr
>>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp


-- 
Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Ovnicraft]

On Wed, Feb 19, 2014 at 6:49 AM, Antony Lesuisse  wrote:

> Yes i forgot to mention that the new report module natively support excel
> reports (or anything else, png, svg, odt...).
>
> For an excel report you should define a controller that output the file.
> For excel 97 you may use xlwt, for excel 2007 and above you could use qweb
> with the bloated office xml format xlsx


Good news for Qweb but please release documentation about report engine
everything will be easy for everybody.

Regards,

> .
>
> @http.route('/mymodule/report/mymodel_excel97_report1/',
> type='http', auth="user")
> def export_xls(self,ids):
> workbook = xlwt.Workbook()
> (...)
>response = request.make_response(None, headers=[('Content-Type',
> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
> filename=table.xls;')])
>workbook.save(response.stream)
>return response
>
> Then you define a 'qweb-pdf' report (yes we need to rename this into
> 'controller').
>
> We will add an example in the report module.
>
>
> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>
>> Antony,
>>
>> What about generating spreadsheets or text documents? Have you looked for
>> something like wkhtmltopdf that is capable of generating a xls, doc, ods
>> or
>> odt from an html? Is it in your plans?
>>
>> This could be, I think, the missing feature to ensure the community is on
>> board with this change.
>>
>> I really like the qweb report engine. You guys have done a great job. We
>> will
>> start migrating our main report set for the localization by the end of
>> March.
>> Do you have an idea of when will it be merged in trunk (more or less)?
>> This
>> can help to plan our work to prepare for v8.
>>
>> Regards,
>> --
>> PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
>> cualquier error de escritura.
>>
>> Carlos Vásquez
>> CTO · Director de Ingeniería
>>
>> carlos.vasq...@clearcorp.co.cr 
>>
>> CR: +(506) 4000 CORP (4000 2677)
>> US: +1 (786) 472-4267
>> Cel: +(506) 8351 4484
>> skype: crvasquez
>> twitter: cvclearcorp
>>
>> 300 m. Este de la Escuela
>> Calle de Platanares
>> 11402 San Jerónimo, Moravia
>> San José, Costa Rica
>>
>> http://www.clearcorp.co.cr
>>
>>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Cristian Salamea
@ovnicraft
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Francesco Apruzzese]

and +1000 here!!

Il 19/02/2014 13:39, Dave Burkholder ha scritto:

+1,000

On 2/19/2014 6:54 AM, Pedro Manuel Baeza Romero wrote:
Hi, Antony, ¡excellent news! Why don't you develop this option 
directly in the core and give people the possibility to select output 
format on report definition the same as Aeroo does?


About my question of the other mail, do you plan to improve report 
engine with community feedback?


Regards.


2014-02-19 12:49 GMT+01:00 Antony Lesuisse >:


Yes i forgot to mention that the new report module natively
support excel reports (or anything else, png, svg, odt...).

For an excel report you should define a controller that output
the file. For excel 97 you may use xlwt, for excel 2007 and above
you could use qweb with the bloated office xml format xlsx.

@http.route('/mymodule/report/mymodel_excel97_report1/',
type='http', auth="user")
def export_xls(self,ids):
workbook = xlwt.Workbook()
(...)
   response = request.make_response(None,
headers=[('Content-Type', 'application/vnd.ms-excel'),
('Content-Disposition', 'attachment; filename=table.xls;')])
   workbook.save(response.stream)
   return response

Then you define a 'qweb-pdf' report (yes we need to rename this
into 'controller').

We will add an example in the report module.


On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text documents? Have
you looked for
something like wkhtmltopdf that is capable of generating a
xls, doc, ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the
community is on
board with this change.

I really like the qweb report engine. You guys have done a
great job. We will
start migrating our main report set for the localization by
the end of March.
Do you have an idea of when will it be merged in trunk (more
or less)? This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe
la brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr

>

CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267 
Cel: +(506) 8351 4484 
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr


___
Mailing list: https://launchpad.net/~openerp-community

Post to : openerp-community@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openerp-community

More help   : https://help.launchpad.net/ListHelp




___
Mailing list:https://launchpad.net/~openerp-community
Post to :openerp-community@lists.launchpad.net
Unsubscribe :https://launchpad.net/~openerp-community
More help   :https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Dave Burkholder]

+1,000

On 2/19/2014 6:54 AM, Pedro Manuel Baeza Romero wrote:
Hi, Antony, ¡excellent news! Why don't you develop this option 
directly in the core and give people the possibility to select output 
format on report definition the same as Aeroo does?


About my question of the other mail, do you plan to improve report 
engine with community feedback?


Regards.


2014-02-19 12:49 GMT+01:00 Antony Lesuisse >:


Yes i forgot to mention that the new report module natively
support excel reports (or anything else, png, svg, odt...).

For an excel report you should define a controller that output the
file. For excel 97 you may use xlwt, for excel 2007 and above you
could use qweb with the bloated office xml format xlsx.

@http.route('/mymodule/report/mymodel_excel97_report1/',
type='http', auth="user")
def export_xls(self,ids):
workbook = xlwt.Workbook()
(...)
   response = request.make_response(None,
headers=[('Content-Type', 'application/vnd.ms-excel'),
('Content-Disposition', 'attachment; filename=table.xls;')])
   workbook.save(response.stream)
   return response

Then you define a 'qweb-pdf' report (yes we need to rename this
into 'controller').

We will add an example in the report module.


On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text documents? Have you
looked for
something like wkhtmltopdf that is capable of generating a
xls, doc, ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the
community is on
board with this change.

I really like the qweb report engine. You guys have done a
great job. We will
start migrating our main report set for the localization by
the end of March.
Do you have an idea of when will it be merged in trunk (more
or less)? This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe
la brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr

>

CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267 
Cel: +(506) 8351 4484 
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr


___
Mailing list: https://launchpad.net/~openerp-community

Post to : openerp-community@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openerp-community

More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Pedro Manuel Baeza Romero]

Hi, Antony, ¡excellent news! Why don't you develop this option directly in
the core and give people the possibility to select output format on report
definition the same as Aeroo does?

About my question of the other mail, do you plan to improve report engine
with community feedback?

Regards.


2014-02-19 12:49 GMT+01:00 Antony Lesuisse :

> Yes i forgot to mention that the new report module natively support excel
> reports (or anything else, png, svg, odt...).
>
> For an excel report you should define a controller that output the file.
> For excel 97 you may use xlwt, for excel 2007 and above you could use qweb
> with the bloated office xml format xlsx.
>
> @http.route('/mymodule/report/mymodel_excel97_report1/',
> type='http', auth="user")
> def export_xls(self,ids):
> workbook = xlwt.Workbook()
> (...)
>response = request.make_response(None, headers=[('Content-Type',
> 'application/vnd.ms-excel'), ('Content-Disposition', 'attachment;
> filename=table.xls;')])
>workbook.save(response.stream)
>return response
>
> Then you define a 'qweb-pdf' report (yes we need to rename this into
> 'controller').
>
> We will add an example in the report module.
>
>
> On 02/19/2014 06:45 AM, Carlos Vásquez wrote:
>
>> Antony,
>>
>> What about generating spreadsheets or text documents? Have you looked for
>> something like wkhtmltopdf that is capable of generating a xls, doc, ods
>> or
>> odt from an html? Is it in your plans?
>>
>> This could be, I think, the missing feature to ensure the community is on
>> board with this change.
>>
>> I really like the qweb report engine. You guys have done a great job. We
>> will
>> start migrating our main report set for the localization by the end of
>> March.
>> Do you have an idea of when will it be merged in trunk (more or less)?
>> This
>> can help to plan our work to prepare for v8.
>>
>> Regards,
>> --
>> PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
>> cualquier error de escritura.
>>
>> Carlos Vásquez
>> CTO · Director de Ingeniería
>>
>> carlos.vasq...@clearcorp.co.cr 
>>
>> CR: +(506) 4000 CORP (4000 2677)
>> US: +1 (786) 472-4267
>> Cel: +(506) 8351 4484
>> skype: crvasquez
>> twitter: cvclearcorp
>>
>> 300 m. Este de la Escuela
>> Calle de Platanares
>> 11402 San Jerónimo, Moravia
>> San José, Costa Rica
>>
>> http://www.clearcorp.co.cr
>>
>>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Antony Lesuisse]

Yes i forgot to mention that the new report module natively support excel 
reports (or anything else, png, svg, odt...).


For an excel report you should define a controller that output the file. For 
excel 97 you may use xlwt, for excel 2007 and above you could use qweb with 
the bloated office xml format xlsx.


@http.route('/mymodule/report/mymodel_excel97_report1/', type='http', 
auth="user")

def export_xls(self,ids):
workbook = xlwt.Workbook()
(...)
   response = request.make_response(None, headers=[('Content-Type', 
'application/vnd.ms-excel'), ('Content-Disposition', 'attachment; 
filename=table.xls;')])

   workbook.save(response.stream)
   return response

Then you define a 'qweb-pdf' report (yes we need to rename this into 
'controller').


We will add an example in the report module.

On 02/19/2014 06:45 AM, Carlos Vásquez wrote:

Antony,

What about generating spreadsheets or text documents? Have you looked for
something like wkhtmltopdf that is capable of generating a xls, doc, ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the community is on
board with this change.

I really like the qweb report engine. You guys have done a great job. We will
start migrating our main report set for the localization by the end of March.
Do you have an idea of when will it be merged in trunk (more or less)? This
can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr 
CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267
Cel: +(506) 8351 4484
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr



___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Simone Orsi]

Yep, a lot of improvements have been made on that side. You can check the
log here https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.0.

Speaking of the internal report engine: one should not care about the
internal API and machinery as long as is flexible and pluggable.

You should be able to register your own templating engine that takes in
context/objects data and spits out HTML. That's it.

Internal report system should only care about giving you hooks and api for
managing actions and settings. By default the report machinery should call
the default QWeb component for generating HTML. The you can say "use my XXX
engine to produce HTML", and that's it.

No migration needed for older reports. Just some adjustments into report
modules (webkit, aeroo, whatever).

That's component architecture, baby! :)

Cheers,
S.


On Wed, Feb 19, 2014 at 9:57 AM, Ferdinand Gassauer wrote:

> On 2014-02-19 12:52, Alan Lord wrote:
>
>> On 19/02/14 08:08, Parthiv Patel wrote:
>>
>>> +1 for Antony's approach, A fully flexible reporting service is
>>> something that can act as a based to build other reporting efforts.
>>>
>>
>> Proper report pagination was a thing we found we could *only* properly
>> achieve using Aeroo. By that I mean when you are wanting to print to pdf a
>> Quote with several pages, we found it quite easy in Aeroo to produce nice
>> reports, table headers printed on every page, you can make sure that the
>> final page contains unique information and that tables & rows break across
>> pages properly.
>>
> tables & rows break across pages properly.: the new wkhtmltopdf v12 does
> exactly this.
>
>
>> Is this now achievable using the new QWeb report tool?
>>
>> Thanks
>>
>> Al
>>
>> (PS: Also, in Aeroo you can easily generate reports in doc/xls etc.)
>>
>> ___
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to : openerp-community@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> --
> Ferdinand
>
>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Ferdinand Gassauer]

On 2014-02-19 12:52, Alan Lord wrote:

On 19/02/14 08:08, Parthiv Patel wrote:

+1 for Antony's approach, A fully flexible reporting service is
something that can act as a based to build other reporting efforts.


Proper report pagination was a thing we found we could *only* properly 
achieve using Aeroo. By that I mean when you are wanting to print to 
pdf a Quote with several pages, we found it quite easy in Aeroo to 
produce nice reports, table headers printed on every page, you can 
make sure that the final page contains unique information and that 
tables & rows break across pages properly.
tables & rows break across pages properly.: the new wkhtmltopdf v12 does 
exactly this.


Is this now achievable using the new QWeb report tool?

Thanks

Al

(PS: Also, in Aeroo you can easily generate reports in doc/xls etc.)

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



--
Ferdinand


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Alan Lord]

On 19/02/14 08:08, Parthiv Patel wrote:

+1 for Antony's approach, A fully flexible reporting service is
something that can act as a based to build other reporting efforts.


Proper report pagination was a thing we found we could *only* properly 
achieve using Aeroo. By that I mean when you are wanting to print to pdf 
a Quote with several pages, we found it quite easy in Aeroo to produce 
nice reports, table headers printed on every page, you can make sure 
that the final page contains unique information and that tables & rows 
break across pages properly.


Is this now achievable using the new QWeb report tool?

Thanks

Al

(PS: Also, in Aeroo you can easily generate reports in doc/xls etc.)

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Parthiv Patel]

+1 for Antony's approach, A fully flexible reporting service is something
that can act as a based to build other reporting efforts.


On Wed, Feb 19, 2014 at 1:20 PM, David Beal  wrote:

> +1 multi format new good practice extended by community
>
> David BEAL
> Akretion
> OpenERP Development - Integration
> +33 (0)6 67 22 86 89
> +33 (0)4 82 53 84 60
>
>
> 2014-02-19 6:45 GMT+01:00 Carlos Vásquez :
> > Antony,
> >
> > What about generating spreadsheets or text documents? Have you looked for
> > something like wkhtmltopdf that is capable of generating a xls, doc, ods
> or
> > odt from an html? Is it in your plans?
> >
> > This could be, I think, the missing feature to ensure the community is on
> > board with this change.
> >
> > I really like the qweb report engine. You guys have done a great job. We
> > will start migrating our main report set for the localization by the end
> of
> > March. Do you have an idea of when will it be merged in trunk (more or
> > less)? This can help to plan our work to prepare for v8.
> >
> > Regards,
> > --
> > PS: escribí este email desde mi teléfono, por favor disculpe la brevedad
> y
> > cualquier error de escritura.
> >
> > Carlos Vásquez
> > CTO · Director de Ingeniería
> >
> > carlos.vasq...@clearcorp.co.cr
> > CR: +(506) 4000 CORP (4000 2677)
> > US: +1 (786) 472-4267
> > Cel: +(506) 8351 4484
> > skype: crvasquez
> > twitter: cvclearcorp
> >
> > 300 m. Este de la Escuela
> > Calle de Platanares
> > 11402 San Jerónimo, Moravia
> > San José, Costa Rica
> >
> > http://www.clearcorp.co.cr
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~openerp-community
> > Post to : openerp-community@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openerp-community
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Thanks & Regards,
Parthiv Patel
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[David Beal]

+1 multi format new good practice extended by community

David BEAL
Akretion
OpenERP Development - Integration
+33 (0)6 67 22 86 89
+33 (0)4 82 53 84 60


2014-02-19 6:45 GMT+01:00 Carlos Vásquez :
> Antony,
>
> What about generating spreadsheets or text documents? Have you looked for
> something like wkhtmltopdf that is capable of generating a xls, doc, ods or
> odt from an html? Is it in your plans?
>
> This could be, I think, the missing feature to ensure the community is on
> board with this change.
>
> I really like the qweb report engine. You guys have done a great job. We
> will start migrating our main report set for the localization by the end of
> March. Do you have an idea of when will it be merged in trunk (more or
> less)? This can help to plan our work to prepare for v8.
>
> Regards,
> --
> PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
> cualquier error de escritura.
>
> Carlos Vásquez
> CTO · Director de Ingeniería
>
> carlos.vasq...@clearcorp.co.cr
> CR: +(506) 4000 CORP (4000 2677)
> US: +1 (786) 472-4267
> Cel: +(506) 8351 4484
> skype: crvasquez
> twitter: cvclearcorp
>
> 300 m. Este de la Escuela
> Calle de Platanares
> 11402 San Jerónimo, Moravia
> San José, Costa Rica
>
> http://www.clearcorp.co.cr
>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Pedro Manuel Baeza Romero]

Hi, Antony/Fabien,

Do you think it's time now to discuss the features of the new qweb report
engine? Do you plan to invest more R&D in it? I consider this basic to
achieve the ultimate report engine and the "only" one.

Regards.


2014-02-19 6:45 GMT+01:00 Carlos Vásquez :

> Antony,
>
> What about generating spreadsheets or text documents? Have you looked for
> something like wkhtmltopdf that is capable of generating a xls, doc, ods or
> odt from an html? Is it in your plans?
>
> This could be, I think, the missing feature to ensure the community is on
> board with this change.
>
> I really like the qweb report engine. You guys have done a great job. We
> will start migrating our main report set for the localization by the end of
> March. Do you have an idea of when will it be merged in trunk (more or
> less)? This can help to plan our work to prepare for v8.
>
> Regards,
> --
> PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
> cualquier error de escritura.
>
> Carlos Vásquez
> CTO · Director de Ingeniería
>
> carlos.vasq...@clearcorp.co.cr
> CR: +(506) 4000 CORP (4000 2677)
> US: +1 (786) 472-4267
> Cel: +(506) 8351 4484
> skype: crvasquez
> twitter: cvclearcorp
>
> 300 m. Este de la Escuela
> Calle de Platanares
> 11402 San Jerónimo, Moravia
> San José, Costa Rica
>
> http://www.clearcorp.co.cr
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Carlos Vásquez]

Antony,

What about generating spreadsheets or text documents? Have you looked for
something like wkhtmltopdf that is capable of generating a xls, doc, ods or
odt from an html? Is it in your plans?

This could be, I think, the missing feature to ensure the community is on
board with this change.

I really like the qweb report engine. You guys have done a great job. We
will start migrating our main report set for the localization by the end of
March. Do you have an idea of when will it be merged in trunk (more or
less)? This can help to plan our work to prepare for v8.

Regards,
--
PS: escribí este email desde mi teléfono, por favor disculpe la brevedad y
cualquier error de escritura.

Carlos Vásquez
CTO · Director de Ingeniería

carlos.vasq...@clearcorp.co.cr
CR: +(506) 4000 CORP (4000 2677)
US: +1 (786) 472-4267
Cel: +(506) 8351 4484
skype: crvasquez
twitter: cvclearcorp

300 m. Este de la Escuela
Calle de Platanares
11402 San Jerónimo, Moravia
San José, Costa Rica

http://www.clearcorp.co.cr
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Ferdinand Gassauer]

On 2014-02-19 04:59, Antony Lesuisse wrote:

Thank you for clarifying this.

IMO such information should be part of OpenERP Marketing activities 
towards partners and would avoid mail threads like this one


The argument
***
2/ OpenERP Enterprise covers custom module migration at a price of 
800EUR/1000 lines of code. One should check the number of lines of code 
per report but it should be something around 200EUR to migrate a report, 
which is nothing. So, I don't think it's a blocking point for a migration.

***
is difficult to sell. And *"... which is nothing" *is a miss 
interpretation of the reality of the market - every cent counts. It is 
either the customer or the partner who has to pay and loses money.
No customer who ordered webkit reports in v6 or v7 is prepared to pay 
extra migration fee during migration to v8.

But as we learned from Antony it will not be necessary.



I would like to add that the new report engine is ONLY an addons, not 
a single server nor weblcient line were touched ! [1]


It means that anyone should be able to do any report engine as a pure 
addons without touching anything in the server.


Our intention is not to close the door to any other kind of report 
engine, it's just to standardise our core addons a single templating 
engine (used both for web and print) and a coherent report system.


Alternative (or specialised) reporting engines are always welcome on 
apps.


[1] We only only cleaned the res_company views for usability, and 
renamed paper_format to rml_paper_format to prepare for the deprecation.


On 02/19/2014 01:45 AM, Antony Lesuisse wrote:

definitions:

- "server/report" is the rml egine with it's funny [[ syntax ]] 6460 
line of code

- "report_webkit" is the c2c jinja2 report engine 611 line of code
- "report" is the new v8 qweb-based report engine 497 line of code

Here is my plan:

v8:

we keep "server/report" and "report_webkit" unchanged, but every 
report in our

addons are converted to qweb.

v9:

we remove "server/report" and "report_webkit" from our repository,
"report_webkit" will be moved to a community repo (like we do for every
deprecated module).

So you should adapt your "report_webkit" reports to the new "report" 
engine,
the main difference is to use qweb templating instead of jinja2. The 
principal

advantage of using qweb instead of jinja2 is the modularity (like forms
views). Qweb directives are xml-attributes (only 7 attributes that 
you need to

learn) so a qweb template is easily extensible using the built in xpath
extention mecanism of openerp (exactly like form views).

In pratice you can now easily extend sale order lines, adding or 
removing a

field, change the style, ... Reports in openerp was the ONLY non-modular
component, it's a huge leap forward.

OpenERP Enterprise customer can ask our migration services to convert 
their

report for a very small fee (part of our custom code migration option).

Converting a "report_webkit" report to a "report" is very easy the 
code doesnt
change, you only need to adapt the template from one syntax to an 
other one. I

think it could almost be automated.

An other interresting change is that report are now REST as every 
report has

an url like:

/report//

and options can be provided

/report//?option1=value1

the above controller output the html version of the report, for the pdf
version you can use

/report/pdf//

This controller simply loads the first one and pass it trough 
wkhtml2pdf and

returns the pdf.

Please TEST it before commenting, the branch is trunk-qweb-report2, and
trunk-qweb-report.

I would like to thank c2c for the "report_webkit" module as it really 
paved
the way to the switch from RML to HTML/CSS, and to the quick 
generation of pdf

using wkhtmltopdf. We keep those feature in "report". We unifed openerp
template engine into qweb an xml-friendly-extensible template engine 
(and

therefore modular like the rest of openerp) that is now used everywhere.

On 02/18/2014 09:27 AM, Nicolas Bessi wrote:

Dear community,

With the approaching release of V8, I'm starting to have questions 
about the

future of the Webkit reports.


*QWeb and Webkit*
*
*
First of all there seems to be a lot of confusions between QWeb 
reports and

Webkit reports.

Qweb reports and Webkit reports are separated reports engines even 
if they

both rely on similar concept.

They both allows you to develop at set of report using an HTML based 
template

language.
But they have some major differences.

AFAIK Qweb reports are view based reports that offer the same 
flexibility than

standards OpenERP views, (inherit, groups, xpath, translation, etc).

Webkit reports rely on an external library (wkhtmltopdf) to generate 
PDF from

HTML.
HTML are generated using mako/jinga templates. Webkit reports were 
created to

desing complex layout (like ESR payment slip) and render huge report
(thousands of pages) without needed a huge machinery.

My opinion is that both report engine are com

Re: [Openerp-community] report_webkit future

[Antony Lesuisse]

I would like to add that the new report engine is ONLY an addons, not a single 
server nor weblcient line were touched ! [1]


It means that anyone should be able to do any report engine as a pure addons 
without touching anything in the server.


Our intention is not to close the door to any other kind of report engine, 
it's just to standardise our core addons a single templating engine (used both 
for web and print) and a coherent report system.


Alternative (or specialised) reporting engines are always welcome on apps.

[1] We only only cleaned the res_company views for usability, and renamed 
paper_format to rml_paper_format to prepare for the deprecation.


On 02/19/2014 01:45 AM, Antony Lesuisse wrote:

definitions:

- "server/report" is the rml egine with it's funny [[ syntax ]] 6460 line of 
code
- "report_webkit" is the c2c jinja2 report engine 611 line of code
- "report" is the new v8 qweb-based report engine 497 line of code

Here is my plan:

v8:

we keep "server/report" and "report_webkit" unchanged, but every report in our
addons are converted to qweb.

v9:

we remove "server/report" and "report_webkit" from our repository,
"report_webkit" will be moved to a community repo (like we do for every
deprecated module).

So you should adapt your "report_webkit" reports to the new "report" engine,
the main difference is to use qweb templating instead of jinja2. The principal
advantage of using qweb instead of jinja2 is the modularity (like forms
views). Qweb directives are xml-attributes (only 7 attributes that you need to
learn) so a qweb template is easily extensible using the built in xpath
extention mecanism of openerp (exactly like form views).

In pratice you can now easily extend sale order lines, adding or removing a
field, change the style, ... Reports in openerp was the ONLY non-modular
component, it's a huge leap forward.

OpenERP Enterprise customer can ask our migration services to convert their
report for a very small fee (part of our custom code migration option).

Converting a "report_webkit" report to a "report" is very easy the code doesnt
change, you only need to adapt the template from one syntax to an other one. I
think it could almost be automated.

An other interresting change is that report are now REST as every report has
an url like:

/report//

and options can be provided

/report//?option1=value1

the above controller output the html version of the report, for the pdf
version you can use

/report/pdf//

This controller simply loads the first one and pass it trough wkhtml2pdf and
returns the pdf.

Please TEST it before commenting, the branch is trunk-qweb-report2, and
trunk-qweb-report.

I would like to thank c2c for the "report_webkit" module as it really paved
the way to the switch from RML to HTML/CSS, and to the quick generation of pdf
using wkhtmltopdf. We keep those feature in "report". We unifed openerp
template engine into qweb an xml-friendly-extensible template engine (and
therefore modular like the rest of openerp) that is now used everywhere.

On 02/18/2014 09:27 AM, Nicolas Bessi wrote:

Dear community,

With the approaching release of V8, I'm starting to have questions about the
future of the Webkit reports.


*QWeb and Webkit*
*
*
First of all there seems to be a lot of confusions between QWeb reports and
Webkit reports.

Qweb reports and Webkit reports are separated reports engines even if they
both rely on similar concept.

They both allows you to develop at set of report using an HTML based template
language.
But they have some major differences.

AFAIK Qweb reports are view based reports that offer the same flexibility than
standards OpenERP views, (inherit, groups, xpath, translation, etc).

Webkit reports rely on an external library (wkhtmltopdf) to generate PDF from
HTML.
HTML are generated using mako/jinga templates. Webkit reports were created to
desing complex layout (like ESR payment slip) and render huge report
(thousands of pages) without needed a huge machinery.

My opinion is that both report engine are complementary at that time.


*Future of Webkit reports*

I have not heard that report_webkit will be deprecated and there are still in
code base.
Camptocamp will continue to maintain existing webkit reports (especially
financial report) but may port to Qweb report that are a better fit for this
technology (PO, SO, etc.)

We will also continue to provide enhancement and support to report_webkit for
next the release.


That said it is not impossible at middle term when we have more feedback on
Qweb report to have convergence of both engines.


Regards

Nicolas



___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-

Re: [Openerp-community] report_webkit future

[Antony Lesuisse]

definitions:

- "server/report" is the rml egine with it's funny [[ syntax ]] 6460 line of 
code
- "report_webkit" is the c2c jinja2 report engine 611 line of code
- "report" is the new v8 qweb-based report engine 497 line of code

Here is my plan:

v8:

we keep "server/report" and "report_webkit" unchanged, but every report in our 
addons are converted to qweb.


v9:

we remove "server/report" and "report_webkit" from our repository, 
"report_webkit" will be moved to a community repo (like we do for every 
deprecated module).


So you should adapt your "report_webkit" reports to the new "report" engine, 
the main difference is to use qweb templating instead of jinja2. The principal 
advantage of using qweb instead of jinja2 is the modularity (like forms 
views). Qweb directives are xml-attributes (only 7 attributes that you need to 
learn) so a qweb template is easily extensible using the built in xpath 
extention mecanism of openerp (exactly like form views).


In pratice you can now easily extend sale order lines, adding or removing a 
field, change the style, ... Reports in openerp was the ONLY non-modular 
component, it's a huge leap forward.


OpenERP Enterprise customer can ask our migration services to convert their 
report for a very small fee (part of our custom code migration option).


Converting a "report_webkit" report to a "report" is very easy the code doesnt 
change, you only need to adapt the template from one syntax to an other one. I 
think it could almost be automated.


An other interresting change is that report are now REST as every report has 
an url like:


/report//

and options can be provided

/report//?option1=value1

the above controller output the html version of the report, for the pdf 
version you can use


/report/pdf//

This controller simply loads the first one and pass it trough wkhtml2pdf and 
returns the pdf.


Please TEST it before commenting, the branch is trunk-qweb-report2, and 
trunk-qweb-report.


I would like to thank c2c for the "report_webkit" module as it really paved 
the way to the switch from RML to HTML/CSS, and to the quick generation of pdf 
using wkhtmltopdf. We keep those feature in "report". We unifed openerp 
template engine into qweb an xml-friendly-extensible template engine (and 
therefore modular like the rest of openerp) that is now used everywhere.


On 02/18/2014 09:27 AM, Nicolas Bessi wrote:

Dear community,

With the approaching release of V8, I'm starting to have questions about the
future of the Webkit reports.


*QWeb and Webkit*
*
*
First of all there seems to be a lot of confusions between QWeb reports and
Webkit reports.

Qweb reports and Webkit reports are separated reports engines even if they
both rely on similar concept.

They both allows you to develop at set of report using an HTML based template
language.
But they have some major differences.

AFAIK Qweb reports are view based reports that offer the same flexibility than
standards OpenERP views, (inherit, groups, xpath, translation, etc).

Webkit reports rely on an external library (wkhtmltopdf) to generate PDF from
HTML.
HTML are generated using mako/jinga templates. Webkit reports were created to
desing complex layout (like ESR payment slip) and render huge report
(thousands of pages) without needed a huge machinery.

My opinion is that both report engine are complementary at that time.


*Future of Webkit reports*

I have not heard that report_webkit will be deprecated and there are still in
code base.
Camptocamp will continue to maintain existing webkit reports (especially
financial report) but may port to Qweb report that are a better fit for this
technology (PO, SO, etc.)

We will also continue to provide enhancement and support to report_webkit for
next the release.


That said it is not impossible at middle term when we have more feedback on
Qweb report to have convergence of both engines.


Regards

Nicolas



___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Fabien Pinckaers]

Hello,

1/ moving from report_webkit to QWeb does not require you to redevelop
everything. The python code remains nearly the same and Jinja/HTML to
Webkit/HTML is quite easy to translate.

2/ OpenERP Enterprise covers custom module migration at a price of
800 EURO/1000 lines of code. One should check the number of lines of code per
report but it should be something around 200 EURO to migrate a report, which is
nothing. So, I don't think it's a blocking point for a migration.

3/ I understand the pain of supporting a technology change --> we had to
invest into converting around 100 reports from v7 to QWeb which is a real
effort on our side. But the final result is worth the effort. With QWeb
reports, everything becomes super easy to customize for your customers.

We should differentiate the reports you already done and the future reports
you will develop (starting from v8). For existing reports, we will announce
as soon as we have taken the decision to keep RML & report_webkit for v7,
v8 or v9. And, in any case, we can handle the migration as part of the
OpenERP Enterprise contract for a very cheap price.


For new reports you will develop starting from v8 I think we should all
(OpenERP SA and the community) go into the QWeb direction rather than
splitting our efforts on different report engines. One can always try to
keep old modules and forward port reports but I think OpenERP will better
evolve if everyone follows the same direction.

Our goal is to make OpenERP become better and better, versions after
versions. We can't improve the overall quality if we always try to keep
legacy stuff.

We finally found a solution that solves all reporting issues (cube with
graph views and QWeb for paper report). If everyone adopt this, starting
from v8, the future of OpenERP will be better and easier for every
developer.



Fabien



On Tue, Feb 18, 2014 at 9:38 PM, Peter Langenberg <
peter.langenb...@bubbles-it.be> wrote:

> The advantage of the report_webkit for many of us is that the guys from
> camptocamp (and others) have written fabulous reports for us it. Our
> customers (and we) have invested a lot of money and time in a complete
> suite of reports that we can throw away.
>
> It will stop some customers from doing migrations, because the migration
> of the custom reports will be too expensive. It's can be a real showstopper
> in a lot of cases.
>
> IMHO the official openerp reports are not always so neat and clean. (I'm
> talking functional now, not techical) and in the 'real world'  users are
> used to them and don't want to change for the official reports.
>
> I think Niels puts it very clear in his mail :
>
> "We should be able to do something smarter with the current landscape
> than just throwing out working modules especially since every reporting
> engine so far each has it's own set of missing features."
>
> As Nicolas puts in his mail, what about maintenance contracts (v6.1 - 7.0
> ...)
>
> And of course we will start to use Qweb reports and if it's better than
> the report_webkit we'll be very happy and write all our "future" reports
> with it.
>
> Peter
>
> PS : I realy like the things in v8 I've seen until now.
>
>
> 2014-02-18 20:48 GMT+01:00 Fabien Pinckaers :
>
>
>>
>> On 02/18/2014 05:55 PM, Peter Langenberg wrote:
>> > Fabien,
>> >
>> > Can you assure us that the qweb engine will support everyones needs ?
>>
>> I can't assure you such a thing since I don't know your exact needs.
>> But, for sure, it satisfy all our requirements for official reports on
>> all official modules. The best is that you check by yourself.
>>
>> I don't see any advantage of RML or report_webkit that the new report
>> engine does not support. (and the new report engine provides a lot of
>> new benefits)
>>
>> Fabien
>>
>> > So we have to throw away all our investments we made in Webkit ?
>> >
>> > Peter
>> >
>> > 2014-02-18 17:36 GMT+01:00 Fabien Pinckaers :
>> >> Hello,
>> >>
>> >> We think we have too much report engines: RML, XSL:RML, report_webkit
>> plus
>> >> all community  addons. We have a lot of report engines because none of
>> them
>> >> were good enough to support everyone's needs.
>> >>
>> >> The new QWeb approach is super clean, so we decided to go for it and
>> invest
>> >> to make it perfect. We reviewed/are reviewing all official reports of
>> >> OpenERP. It's better to have one clean report engine and stick to it.
>> >>
>> >> It's a huge improvement because its based on all the "normal"
>> technologies
>> >> of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb,
>> tests...
>> >> So, all the improvements we do on the OpenERP framework or report
>> engine
>> >> benefit to others parts of OpenERP.
>> >>
>> >> I still do not know if we will deprecate report_webkit in v8 or v9,
>> but I
>> >> prefer to tell you now, so that you can already base your future
>> decisions
>> >> on the future technology.
>> >>
>> >> Fabien
>> >>
>> >>
>> >>
>> >>
>> >> On Tue, Feb 18, 2014 at 5:01 PM, Nicolas Bes

Re: [Openerp-community] report_webkit future

[Raphael Valyi]

Hello Peter,

I think many share your analysis. Basically it's a matter of C2C +
community peer reviewed quality vs something offshored no very battle
tested yet (reminder we discovered the v7 contact woes like 4 months after
v7 was released..). That being said, I think the qweb reports for the core
will be a tremendous improvement over the RML and boost the productivity of
integrations in the long term and this is absolutely welcomed.

Now I think it should be easy to maintain the webkit report as an extra
module or as a small OCB/other tracking branch patch, no? That wouldn't be
like the 1st time. We used Aeroo this way for years after all (and will
probably keep using it in its niche of "I want this .doc report with these
nested tables, can you do it for tomorrow please?").

@Fabien,
you were talking about OpenERP image these days. I think for that kind of
decision, to build the image of a serious company, you should try to plan
like at least 18 months in advance what will be the supported reporting
engines. That is, if you announced such a drop like 1 year ago, it was
legitimate to drop it. Now if didn't announce it (you didn't), probably
it's wiser to supported with a deprecated status in v8 and remove it from
core in v9 only. If you cannot afford planning so far, then please delegate
more to the OCA community; just a suggestion.

Imagine if Linux kernel were telling us, you know we won't support ext3
partitions anymore in the next version in 4 months, you wouldn't be very
happy at OpenERP SA. So, in order to build a better image, I suggest that
everytime you take a decision, you try to figure out how will react people
depending on your open source component by transposing how would OpenERP SA
react if Linux, or Postgresql or Python would "pivot" their business model
overnight as if they were alone in the boat. Just thinking loud...

Regards


On Tue, Feb 18, 2014 at 5:38 PM, Peter Langenberg <
peter.langenb...@bubbles-it.be> wrote:

> The advantage of the report_webkit for many of us is that the guys from
> camptocamp (and others) have written fabulous reports for us it. Our
> customers (and we) have invested a lot of money and time in a complete
> suite of reports that we can throw away.
>
> It will stop some customers from doing migrations, because the migration
> of the custom reports will be too expensive. It's can be a real showstopper
> in a lot of cases.
>
> IMHO the official openerp reports are not always so neat and clean. (I'm
> talking functional now, not techical) and in the 'real world'  users are
> used to them and don't want to change for the official reports.
>
> I think Niels puts it very clear in his mail :
>
> "We should be able to do something smarter with the current landscape
> than just throwing out working modules especially since every reporting
> engine so far each has it's own set of missing features."
>
> As Nicolas puts in his mail, what about maintenance contracts (v6.1 - 7.0
> ...)
>
> And of course we will start to use Qweb reports and if it's better than
> the report_webkit we'll be very happy and write all our "future" reports
> with it.
>
> Peter
>
> PS : I realy like the things in v8 I've seen until now.
>
>
> 2014-02-18 20:48 GMT+01:00 Fabien Pinckaers :
>
>
>>
>> On 02/18/2014 05:55 PM, Peter Langenberg wrote:
>> > Fabien,
>> >
>> > Can you assure us that the qweb engine will support everyones needs ?
>>
>> I can't assure you such a thing since I don't know your exact needs.
>> But, for sure, it satisfy all our requirements for official reports on
>> all official modules. The best is that you check by yourself.
>>
>> I don't see any advantage of RML or report_webkit that the new report
>> engine does not support. (and the new report engine provides a lot of
>> new benefits)
>>
>> Fabien
>>
>> > So we have to throw away all our investments we made in Webkit ?
>> >
>> > Peter
>> >
>> > 2014-02-18 17:36 GMT+01:00 Fabien Pinckaers :
>> >> Hello,
>> >>
>> >> We think we have too much report engines: RML, XSL:RML, report_webkit
>> plus
>> >> all community  addons. We have a lot of report engines because none of
>> them
>> >> were good enough to support everyone's needs.
>> >>
>> >> The new QWeb approach is super clean, so we decided to go for it and
>> invest
>> >> to make it perfect. We reviewed/are reviewing all official reports of
>> >> OpenERP. It's better to have one clean report engine and stick to it.
>> >>
>> >> It's a huge improvement because its based on all the "normal"
>> technologies
>> >> of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb,
>> tests...
>> >> So, all the improvements we do on the OpenERP framework or report
>> engine
>> >> benefit to others parts of OpenERP.
>> >>
>> >> I still do not know if we will deprecate report_webkit in v8 or v9,
>> but I
>> >> prefer to tell you now, so that you can already base your future
>> decisions
>> >> on the future technology.
>> >>
>> >> Fabien
>> >>
>> >>
>> >>
>> >>
>> >> On Tue, Feb 18, 2

Re: [Openerp-community] report_webkit future

[Peter Langenberg]

The advantage of the report_webkit for many of us is that the guys from
camptocamp (and others) have written fabulous reports for us it. Our
customers (and we) have invested a lot of money and time in a complete
suite of reports that we can throw away.

It will stop some customers from doing migrations, because the migration of
the custom reports will be too expensive. It's can be a real showstopper in
a lot of cases.

IMHO the official openerp reports are not always so neat and clean. (I'm
talking functional now, not techical) and in the 'real world'  users are
used to them and don't want to change for the official reports.

I think Niels puts it very clear in his mail :

"We should be able to do something smarter with the current landscape than
just throwing out working modules especially since every reporting engine
so far each has it's own set of missing features."

As Nicolas puts in his mail, what about maintenance contracts (v6.1 - 7.0
...)

And of course we will start to use Qweb reports and if it's better than the
report_webkit we'll be very happy and write all our "future" reports with
it.

Peter

PS : I realy like the things in v8 I've seen until now.


2014-02-18 20:48 GMT+01:00 Fabien Pinckaers :

>
>
> On 02/18/2014 05:55 PM, Peter Langenberg wrote:
> > Fabien,
> >
> > Can you assure us that the qweb engine will support everyones needs ?
>
> I can't assure you such a thing since I don't know your exact needs.
> But, for sure, it satisfy all our requirements for official reports on
> all official modules. The best is that you check by yourself.
>
> I don't see any advantage of RML or report_webkit that the new report
> engine does not support. (and the new report engine provides a lot of
> new benefits)
>
> Fabien
>
> > So we have to throw away all our investments we made in Webkit ?
> >
> > Peter
> >
> > 2014-02-18 17:36 GMT+01:00 Fabien Pinckaers :
> >> Hello,
> >>
> >> We think we have too much report engines: RML, XSL:RML, report_webkit
> plus
> >> all community  addons. We have a lot of report engines because none of
> them
> >> were good enough to support everyone's needs.
> >>
> >> The new QWeb approach is super clean, so we decided to go for it and
> invest
> >> to make it perfect. We reviewed/are reviewing all official reports of
> >> OpenERP. It's better to have one clean report engine and stick to it.
> >>
> >> It's a huge improvement because its based on all the "normal"
> technologies
> >> of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb,
> tests...
> >> So, all the improvements we do on the OpenERP framework or report engine
> >> benefit to others parts of OpenERP.
> >>
> >> I still do not know if we will deprecate report_webkit in v8 or v9, but
> I
> >> prefer to tell you now, so that you can already base your future
> decisions
> >> on the future technology.
> >>
> >> Fabien
> >>
> >>
> >>
> >>
> >> On Tue, Feb 18, 2014 at 5:01 PM, Nicolas Bessi
> >>  wrote:
> >>>
> >>> Hello,
> >>>
> >>> No offense Fabien, but such an unilateral announce may not be the
> proper
> >>> way to manage this kind of announcement...
> >>>
> >>> I'm also a little bit confused about our v6, v6.1, v7, customer that
> have
> >>> support contract. How OpenERP SA intend migration as report_webkit is
> in
> >>> official addons repository.
> >>>
> >>> Regards
> >>>
> >>> Nicolas
> >>>
> >>>
> >>> 2014-02-18 16:51 GMT+01:00 Axel Mendoza Pupo :
> >>>
>  The solutions to print reports based on HTML DOM combined with
> specific
>  CSS rules have that drawback that notebook pages does not get
> displayed
>  properly, is this resolved already? This must complete the solution to
>  render reports based on HTML DOM. If this is resolved already using
> CSS
>  rules, sorry my mistake.
> 
> 
>  On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony 
> wrote:
> >
> > 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 ?
> >
> >
> > Comparing QWeb to Jinja2 is more accurate indeed.
> >
> > As you probably know, v8 will introduce a reporting engine based on
> QWeb
> > templates that is also using wkthmltopdf to produce PDF reports [1]
> > So you will basically have 2 alternatives to design custom HTML-based
> > reports:
> >  - manual design of Jinja2 templates, with report_webkit
> >  - manual or wysiwyg design of QWeb templates (using the Website
> > Builder)
> >
> > But both will be available for server-side PDF rendering using
> > wkhtmltopdf (which has luckily been receiving some love and important
> > features recently)
> >
> >
> >
> >> 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 

Re: [Openerp-community] report_webkit future

[Fabien Pinckaers]

On 02/18/2014 05:55 PM, Peter Langenberg wrote:
> Fabien,
> 
> Can you assure us that the qweb engine will support everyones needs ?

I can't assure you such a thing since I don't know your exact needs.
But, for sure, it satisfy all our requirements for official reports on
all official modules. The best is that you check by yourself.

I don't see any advantage of RML or report_webkit that the new report
engine does not support. (and the new report engine provides a lot of
new benefits)

Fabien

> So we have to throw away all our investments we made in Webkit ?
> 
> Peter
> 
> 2014-02-18 17:36 GMT+01:00 Fabien Pinckaers :
>> Hello,
>>
>> We think we have too much report engines: RML, XSL:RML, report_webkit plus
>> all community  addons. We have a lot of report engines because none of them
>> were good enough to support everyone's needs.
>>
>> The new QWeb approach is super clean, so we decided to go for it and invest
>> to make it perfect. We reviewed/are reviewing all official reports of
>> OpenERP. It's better to have one clean report engine and stick to it.
>>
>> It's a huge improvement because its based on all the "normal" technologies
>> of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb, tests...
>> So, all the improvements we do on the OpenERP framework or report engine
>> benefit to others parts of OpenERP.
>>
>> I still do not know if we will deprecate report_webkit in v8 or v9, but I
>> prefer to tell you now, so that you can already base your future decisions
>> on the future technology.
>>
>> Fabien
>>
>>
>>
>>
>> On Tue, Feb 18, 2014 at 5:01 PM, Nicolas Bessi
>>  wrote:
>>>
>>> Hello,
>>>
>>> No offense Fabien, but such an unilateral announce may not be the proper
>>> way to manage this kind of announcement...
>>>
>>> I'm also a little bit confused about our v6, v6.1, v7, customer that have
>>> support contract. How OpenERP SA intend migration as report_webkit is in
>>> official addons repository.
>>>
>>> Regards
>>>
>>> Nicolas
>>>
>>>
>>> 2014-02-18 16:51 GMT+01:00 Axel Mendoza Pupo :
>>>
 The solutions to print reports based on HTML DOM combined with specific
 CSS rules have that drawback that notebook pages does not get displayed
 properly, is this resolved already? This must complete the solution to
 render reports based on HTML DOM. If this is resolved already using CSS
 rules, sorry my mistake.


 On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony  wrote:
>
> 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 ?
>
>
> Comparing QWeb to Jinja2 is more accurate indeed.
>
> As you probably know, v8 will introduce a reporting engine based on QWeb
> templates that is also using wkthmltopdf to produce PDF reports [1]
> So you will basically have 2 alternatives to design custom HTML-based
> reports:
>  - manual design of Jinja2 templates, with report_webkit
>  - manual or wysiwyg design of QWeb templates (using the Website
> Builder)
>
> But both will be available for server-side PDF rendering using
> wkhtmltopdf (which has luckily been receiving some love and important
> features recently)
>
>
>
>> 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.
>
>
> Yes, that's one of the points :-)
>
>
>
>> 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.
>
>
> QWeb is the templating engine that renders the HTML output of any page,
> and it comes in two flavors:
> - When you access the back-end (the regular OpenERP web client since
> v6.1), the output is rendered client-side using the Javascript-based QWeb
> engine, automatically combining the QWeb templates of the web client 
> widgets
> - When you access the front-end (plain web pages such as Website, Blogs,
> eCommerce, new in v8), the output is rendered server-side using the
> Python-based QWeb engine, by combining the relevant pages and templates
>
> And in both cases when you use the "Print" button of your browser the
> PDF result is produced by your browser itself [2], based on the current 
> HTML
> DOM combined with specific CSS rules for printin

Re: [Openerp-community] report_webkit future

[Peter Langenberg]

Fabien,

Can you assure us that the qweb engine will support everyones needs ?

So we have to throw away all our investments we made in Webkit ?

Peter

2014-02-18 17:36 GMT+01:00 Fabien Pinckaers :
> Hello,
>
> We think we have too much report engines: RML, XSL:RML, report_webkit plus
> all community  addons. We have a lot of report engines because none of them
> were good enough to support everyone's needs.
>
> The new QWeb approach is super clean, so we decided to go for it and invest
> to make it perfect. We reviewed/are reviewing all official reports of
> OpenERP. It's better to have one clean report engine and stick to it.
>
> It's a huge improvement because its based on all the "normal" technologies
> of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb, tests...
> So, all the improvements we do on the OpenERP framework or report engine
> benefit to others parts of OpenERP.
>
> I still do not know if we will deprecate report_webkit in v8 or v9, but I
> prefer to tell you now, so that you can already base your future decisions
> on the future technology.
>
> Fabien
>
>
>
>
> On Tue, Feb 18, 2014 at 5:01 PM, Nicolas Bessi
>  wrote:
>>
>> Hello,
>>
>> No offense Fabien, but such an unilateral announce may not be the proper
>> way to manage this kind of announcement...
>>
>> I'm also a little bit confused about our v6, v6.1, v7, customer that have
>> support contract. How OpenERP SA intend migration as report_webkit is in
>> official addons repository.
>>
>> Regards
>>
>> Nicolas
>>
>>
>> 2014-02-18 16:51 GMT+01:00 Axel Mendoza Pupo :
>>
>>> The solutions to print reports based on HTML DOM combined with specific
>>> CSS rules have that drawback that notebook pages does not get displayed
>>> properly, is this resolved already? This must complete the solution to
>>> render reports based on HTML DOM. If this is resolved already using CSS
>>> rules, sorry my mistake.
>>>
>>>
>>> On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony  wrote:

 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 ?


 Comparing QWeb to Jinja2 is more accurate indeed.

 As you probably know, v8 will introduce a reporting engine based on QWeb
 templates that is also using wkthmltopdf to produce PDF reports [1]
 So you will basically have 2 alternatives to design custom HTML-based
 reports:
  - manual design of Jinja2 templates, with report_webkit
  - manual or wysiwyg design of QWeb templates (using the Website
 Builder)

 But both will be available for server-side PDF rendering using
 wkhtmltopdf (which has luckily been receiving some love and important
 features recently)



> 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.


 Yes, that's one of the points :-)



> 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.


 QWeb is the templating engine that renders the HTML output of any page,
 and it comes in two flavors:
 - When you access the back-end (the regular OpenERP web client since
 v6.1), the output is rendered client-side using the Javascript-based QWeb
 engine, automatically combining the QWeb templates of the web client 
 widgets
 - When you access the front-end (plain web pages such as Website, Blogs,
 eCommerce, new in v8), the output is rendered server-side using the
 Python-based QWeb engine, by combining the relevant pages and templates

 And in both cases when you use the "Print" button of your browser the
 PDF result is produced by your browser itself [2], based on the current 
 HTML
 DOM combined with specific CSS rules for printing.
 Server-side PDFs are only rendered when you call a specific report URL,
 such as the new /report/pdf route in Simon's branch [1].



 [1]
 http://openerp-community.2306076.n4.nabble.com/Openerp-community-tests-feedbacks-for-the-new-reporting-tt4644385.html
 [2] Incidentally, if you are using Chrome, the underlying engine is
 almost the same as what wkhtmltopdf uses.

 ___
 Mailing list: https://launchpad.net/~openerp-community
 Post to :

Re: [Openerp-community] report_webkit future

[Fabien Pinckaers]

Hello,

We think we have too much report engines: RML, XSL:RML, report_webkit plus
all community  addons. We have a lot of report engines because none of them
were good enough to support everyone's needs.

The new QWeb approach is super clean, so we decided to go for it and invest
to make it perfect. We reviewed/are reviewing all official reports of
OpenERP. It's better to have one clean report engine and stick to it.

It's a huge improvement because its based on all the "normal" technologies
of OpenERP; views, translation mechanism, CMS/Inline edition, QWeb,
tests... So, all the improvements we do on the OpenERP framework or report
engine benefit to others parts of OpenERP.

I still do not know if we will deprecate report_webkit in v8 or v9, but I
prefer to tell you now, so that you can already base your future decisions
on the future technology.

Fabien




On Tue, Feb 18, 2014 at 5:01 PM, Nicolas Bessi  wrote:

> Hello,
>
> No offense Fabien, but such an unilateral announce may not be the proper
> way to manage this kind of announcement...
>
> I'm also a little bit confused about our v6, v6.1, v7, customer that have
> support contract. How OpenERP SA intend migration as report_webkit is in
> official addons repository.
>
> Regards
>
> Nicolas
>
>
> 2014-02-18 16:51 GMT+01:00 Axel Mendoza Pupo :
>
> The solutions to print reports based on HTML DOM combined with specific
>> CSS rules have that drawback that notebook pages does not get displayed
>> properly, is this resolved already? This must complete the solution to
>> render reports based on HTML DOM. If this is resolved already using CSS
>> rules, sorry my mistake.
>>
>>
>> On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony  wrote:
>>
>>> 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 ?

>>>
>>> Comparing QWeb to Jinja2 is more accurate indeed.
>>>
>>> As you probably know, v8 will introduce a reporting engine based on QWeb
>>> templates that is also using wkthmltopdf to produce PDF reports [1]
>>> So you will basically have 2 alternatives to design custom HTML-based
>>> reports:
>>>  - manual design of Jinja2 templates, with report_webkit
>>>  - manual or wysiwyg design of QWeb templates (using the Website Builder)
>>>
>>> But both will be available for server-side PDF rendering using
>>> wkhtmltopdf (which has luckily been receiving some love and important
>>> features recently)
>>>
>>>
>>>
>>>  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.

>>>
>>> Yes, that's one of the points :-)
>>>
>>>
>>>
>>>  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.

>>>
>>> QWeb is the templating engine that renders the HTML output of any page,
>>> and it comes in two flavors:
>>> - When you access the back-end (the regular OpenERP web client since
>>> v6.1), the output is rendered client-side using the Javascript-based QWeb
>>> engine, automatically combining the QWeb templates of the web client widgets
>>> - When you access the front-end (plain web pages such as Website, Blogs,
>>> eCommerce, new in v8), the output is rendered server-side using the
>>> Python-based QWeb engine, by combining the relevant pages and templates
>>>
>>> And in both cases when you use the "Print" button of your browser the
>>> PDF result is produced by your browser itself [2], based on the current
>>> HTML DOM combined with specific CSS rules for printing.
>>> Server-side PDFs are only rendered when you call a specific report URL,
>>> such as the new /report/pdf route in Simon's branch [1].
>>>
>>>
>>>
>>> [1] http://openerp-community.2306076.n4.nabble.com/Openerp-
>>> community-tests-feedbacks-for-the-new-reporting-tt4644385.html
>>> [2] Incidentally, if you are using Chrome, the underlying engine is
>>> almost the same as what wkhtmltopdf uses.
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openerp-community
>>> Post to : openerp-community@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openerp-community
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.ne

Re: [Openerp-community] report_webkit future

[Niels Huylebroeck]

Would it not be more appropriate to simply allow easier definition of html
rendering functions / modules ?
This way you can have one model (ir.actions.report.xml) (oh, an old name
:-) which could define two fields (instead of the current single type
field):
* rendering engine
converting from source file and applying data model
* output format
'pdf', 'html', 'xls', '...'

Any number of module can add either a rendering function or an output
format perhaps it's also convenient to convene on an single fixed
intermediate model (such as html would be fine for now I presume).
Otherwise one would have to define which output formats can be used on
which sort of output from the rendering engine.

Right now we have these reporting solutions:
* rml
* xml/xsl
* webkit (v7 is mako->html->pdf, trunk is jinja2->html->pdf)
* aeroo (odt -> odt (with data) -> xls/doc/odt/pdf)

You can see each of them have a source file (covered in
ir.actions.report.xml by report_file)
Not all of them have the same intermediate file (aeroo can however have
html as final out afaik)
We should be able to do something smarter with the current landscape than
just throwing out working modules especially since every reporting engine
so far each has it's own set of missing features.

Regards,
Niels
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Niels Huylebroeck]

Just wanted to add a good read about the refactoring we currently need for
ir.actions.report.*:

http://www.codinghorror.com/blog/2013/07/rule-of-three.html

We now have 5 reporting engines and have a decent overview of how they work
differently to each other. So now we can refactor the ir.actions.report
action in a way that would reduce each of the individual reporting modules
to a simple module which hooks into a new and improved ir.actions.report
This will reduce maintenance cost and keep any reporting module viable
until we can find the holy grail of reporting and we all start moving
towards that one perfect solution. Because we all know it exists but we
just can't agree on which one it exactly is.

Regards,
Niels
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Nicolas Bessi]

Hello Niels,

You have a interesting question here, maybe we should create a new thread
about it on expert mailing list.

Regards

Nicolas


2014-02-18 17:01 GMT+01:00 Niels Huylebroeck :

> Would it not be more appropriate to simply allow easier definition of html
> rendering functions / modules ?
> This way you can have one model (ir.actions.report.xml) (oh, an old name
> :-) which could define two fields (instead of the current single type
> field):
> * rendering engine
> converting from source file and applying data model
> * output format
> 'pdf', 'html', 'xls', '...'
>
> Any number of module can add either a rendering function or an output
> format perhaps it's also convenient to convene on an single fixed
> intermediate model (such as html would be fine for now I presume).
> Otherwise one would have to define which output formats can be used on
> which sort of output from the rendering engine.
>
> Right now we have these reporting solutions:
> * rml
> * xml/xsl
>  * webkit (v7 is mako->html->pdf, trunk is jinja2->html->pdf)
> * aeroo (odt -> odt (with data) -> xls/doc/odt/pdf)
>
> You can see each of them have a source file (covered in
> ir.actions.report.xml by report_file)
> Not all of them have the same intermediate file (aeroo can however have
> html as final out afaik)
> We should be able to do something smarter with the current landscape than
> just throwing out working modules especially since every reporting engine
> so far each has it's own set of missing features.
>
> Regards,
> Niels
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Nicolas Bessi]

Hello,

No offense Fabien, but such an unilateral announce may not be the proper
way to manage this kind of announcement...

I'm also a little bit confused about our v6, v6.1, v7, customer that have
support contract. How OpenERP SA intend migration as report_webkit is in
official addons repository.

Regards

Nicolas


2014-02-18 16:51 GMT+01:00 Axel Mendoza Pupo :

> The solutions to print reports based on HTML DOM combined with specific
> CSS rules have that drawback that notebook pages does not get displayed
> properly, is this resolved already? This must complete the solution to
> render reports based on HTML DOM. If this is resolved already using CSS
> rules, sorry my mistake.
>
>
> On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony  wrote:
>
>> 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 ?
>>>
>>
>> Comparing QWeb to Jinja2 is more accurate indeed.
>>
>> As you probably know, v8 will introduce a reporting engine based on QWeb
>> templates that is also using wkthmltopdf to produce PDF reports [1]
>> So you will basically have 2 alternatives to design custom HTML-based
>> reports:
>>  - manual design of Jinja2 templates, with report_webkit
>>  - manual or wysiwyg design of QWeb templates (using the Website Builder)
>>
>> But both will be available for server-side PDF rendering using
>> wkhtmltopdf (which has luckily been receiving some love and important
>> features recently)
>>
>>
>>
>>  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.
>>>
>>
>> Yes, that's one of the points :-)
>>
>>
>>
>>  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.
>>>
>>
>> QWeb is the templating engine that renders the HTML output of any page,
>> and it comes in two flavors:
>> - When you access the back-end (the regular OpenERP web client since
>> v6.1), the output is rendered client-side using the Javascript-based QWeb
>> engine, automatically combining the QWeb templates of the web client widgets
>> - When you access the front-end (plain web pages such as Website, Blogs,
>> eCommerce, new in v8), the output is rendered server-side using the
>> Python-based QWeb engine, by combining the relevant pages and templates
>>
>> And in both cases when you use the "Print" button of your browser the PDF
>> result is produced by your browser itself [2], based on the current HTML
>> DOM combined with specific CSS rules for printing.
>> Server-side PDFs are only rendered when you call a specific report URL,
>> such as the new /report/pdf route in Simon's branch [1].
>>
>>
>>
>> [1] http://openerp-community.2306076.n4.nabble.com/Openerp-
>> community-tests-feedbacks-for-the-new-reporting-tt4644385.html
>> [2] Incidentally, if you are using Chrome, the underlying engine is
>> almost the same as what wkhtmltopdf uses.
>>
>> ___
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to : openerp-community@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Nicolas Bessi]

Hello,

Maybe my intentions were not clear enough, actually I was not comparing
wkhtmltopdf and Qweb but the module report_webkit with new QWeb repot
system.
The objective of this thread is to disambiguate the current situation with
the two reports system, and inform community that Camptocamp will
maintained report_webkit ecosystem for release 8.

For the other points, Olivier gave all needed information : )

Regards

Nicolas




2014-02-18 11:53 GMT+01:00 Niels Huylebroeck :

> 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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Axel Mendoza Pupo]

The solutions to print reports based on HTML DOM combined with specific CSS
rules have that drawback that notebook pages does not get displayed
properly, is this resolved already? This must complete the solution to
render reports based on HTML DOM. If this is resolved already using CSS
rules, sorry my mistake.


On Tue, Feb 18, 2014 at 10:01 AM, Olivier Dony  wrote:

> 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 ?
>>
>
> Comparing QWeb to Jinja2 is more accurate indeed.
>
> As you probably know, v8 will introduce a reporting engine based on QWeb
> templates that is also using wkthmltopdf to produce PDF reports [1]
> So you will basically have 2 alternatives to design custom HTML-based
> reports:
>  - manual design of Jinja2 templates, with report_webkit
>  - manual or wysiwyg design of QWeb templates (using the Website Builder)
>
> But both will be available for server-side PDF rendering using wkhtmltopdf
> (which has luckily been receiving some love and important features recently)
>
>
>
>  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.
>>
>
> Yes, that's one of the points :-)
>
>
>
>  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.
>>
>
> QWeb is the templating engine that renders the HTML output of any page,
> and it comes in two flavors:
> - When you access the back-end (the regular OpenERP web client since
> v6.1), the output is rendered client-side using the Javascript-based QWeb
> engine, automatically combining the QWeb templates of the web client widgets
> - When you access the front-end (plain web pages such as Website, Blogs,
> eCommerce, new in v8), the output is rendered server-side using the
> Python-based QWeb engine, by combining the relevant pages and templates
>
> And in both cases when you use the "Print" button of your browser the PDF
> result is produced by your browser itself [2], based on the current HTML
> DOM combined with specific CSS rules for printing.
> Server-side PDFs are only rendered when you call a specific report URL,
> such as the new /report/pdf route in Simon's branch [1].
>
>
>
> [1] http://openerp-community.2306076.n4.nabble.com/Openerp-
> community-tests-feedbacks-for-the-new-reporting-tt4644385.html
> [2] Incidentally, if you are using Chrome, the underlying engine is almost
> the same as what wkhtmltopdf uses.
>
> ___
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Fabien Pinckaers]

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@lists.launchpad.net
> 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

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Olivier Dony]

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 ?


Comparing QWeb to Jinja2 is more accurate indeed.

As you probably know, v8 will introduce a reporting engine based on QWeb 
templates that is also using wkthmltopdf to produce PDF reports [1]

So you will basically have 2 alternatives to design custom HTML-based reports:
 - manual design of Jinja2 templates, with report_webkit
 - manual or wysiwyg design of QWeb templates (using the Website Builder)

But both will be available for server-side PDF rendering using wkhtmltopdf 
(which has luckily been receiving some love and important features recently)




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.


Yes, that's one of the points :-)



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.


QWeb is the templating engine that renders the HTML output of any page, and it 
comes in two flavors:
- When you access the back-end (the regular OpenERP web client since v6.1), the 
output is rendered client-side using the Javascript-based QWeb engine, 
automatically combining the QWeb templates of the web client widgets
- When you access the front-end (plain web pages such as Website, Blogs, 
eCommerce, new in v8), the output is rendered server-side using the 
Python-based QWeb engine, by combining the relevant pages and templates


And in both cases when you use the "Print" button of your browser the PDF 
result is produced by your browser itself [2], based on the current HTML DOM 
combined with specific CSS rules for printing.
Server-side PDFs are only rendered when you call a specific report URL, such as 
the new /report/pdf route in Simon's branch [1].




[1] 
http://openerp-community.2306076.n4.nabble.com/Openerp-community-tests-feedbacks-for-the-new-reporting-tt4644385.html
[2] Incidentally, if you are using Chrome, the underlying engine is almost the 
same as what wkhtmltopdf uses.


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] report_webkit future

[Niels Huylebroeck]

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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp