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
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
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
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 ?
>
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
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
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.
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 ?
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.
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 so
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 perfec
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 commun
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. T
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 migrat
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 cor
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 ch
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"
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
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 o
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
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 abou
+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 l
+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 - Inte
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 wa
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 usin
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 a
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 xm
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.
20
+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 pl
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
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 exc
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
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 nic
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
>
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
Camptoc
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 doc
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 al
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
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 :-)
>>
>>
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 More
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-c
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
Unsubs
42 matches
Mail list logo
