@sraps
> Could you elaborate on this? We have spent a lot of time to compare numerous > options of reporting engine (both existing and those which could be > implemented), but there is nothing like report_openoffice. We tried all too!!! report_openoffice - jasper and others, and as i said, it was only an opinion, the main point is. All report engines have good and bad points, but we need have things as webkit and reportlab, why? simply, openoffice will be abandoned by oracle i'm almost sure of this, but if we have some integrated tool, with grafical interface and WYSWYG tools ALL integrated, and ALL documented is the better option and we will not depend of none external tool. My english is not very good, sorry i will try to explain my point of view., I am trying to say that OpenOffice is a good tool, yeah!, but is not for make reports, it will be almost impossible apply all options on a calc or writter doc on a report without spend a lot of time to develop the conector that at the end of day will be converted to a low level doc to get this, the developments should be in other direction from the low level [HTML AND RML] to high level [WYSWYG], but this is my opinion i can be wrong. If you check this links: http://www.reportlab.com/software/documentation/rml-samples/ and this one: http://www.reportlab.com/docs/rml2pdf-userguide.pdf I think you will be able to make ALL what you need, and if you asembly a good own library of snnipets like samples is all what you need. We will not need to write documentation, all is done, the problem is the incomplete implementation, not the tool. All this combined with a good WYSWYG tool to make the look and feel easy as Borja said to not spend more than 1 minute changing a bold font or a border, you should be able to make very powerful tools. a "preview button" with a widget as "html_widget" should be enought. BTW, this is not for become this a war of report engines, is for invite to join efforts in make THE BEST report engine for developers not for end users as priority right now, if we spend time in develop (for now) report engines for end users they will be incomplete for at least 2 more years. Some times you need to spend 1 or 2 hours of try an error to look how was implemented some feature of Jasper - Report_openoffice - WebKit - reportlab, ALL are incompletes in one way or another, but, the only one that works with a really good precision is RL, we think it should be implemented COMPLETE and the power will be unlimited. I think a very good report NEEDS very good people behind, is not only to see good and pretty only (even this is important too!), is to see _the correct information_. In all cases the _only_ thing that a team spend less time with jasper or OO is in the look and feel all report engines actually needs programming and this is not bad this is a reality in all ERP systems, if the people behind the construction of a report doesn't have knowledge it will be "fastly done" but "badly done" in same manner. Conclusion, we need tools to _program_ very good reports, with the correct data, this requires programming knowledge, functional knowledge and documentation by equal, the look and feel, after you try _one time_ is really easy, I repeat, we need one tool whatever it is, with 3 basic characteristics: -- Written on Python. -- Tottally integrated AND implemented. -- Exportable to office and html (OO, Calc, Excel and more) @Borja. @fabien > -> To do a conditional structure (the every day "if then else") you have to > mess with an unintuitive "removeParentNode", how many final users do even > know what a node is? ++1 toally agree, there are a feature available to do that on RL API, but is not implemented, we think it should be done something like this, with a multiline structure of python. [[[ If condition: tag="<para>[[something]]</para> else: tag="<para>[[another_one_opti]]</para> ]]] Look the [[[]]] it means "multiline python" or allow return the direct rml string from the parser and you can do that: <specialTag>[[function_()]]</specialTag> Where function wll return the rml code (as headers are implemented). This feature could be great! regards[/code][/quote] ------------------------ Nhomar Hernandez CTO at http://openerp.netquatro.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=61368#61368 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
