Dear Htgoebel, I tried to contact you privately. Probably I did not succed. So I post here my reply:
I propose that we can think together to a sort of rough specification for this feature, based on your experimental plugin. Then you could propose your conditions and we could share them with the community. So we will reach a common agreement on the spec and the critical mass to finance such a step forward for TinyERP reporting. My idea was to release the financed work with a GPL license and incorporate it in TinyERP, if Tiny agrees (Fabien?). I try to explain this feature as I thought it. Let's call it odt->odt engine. 1) The report template should be an odt file with the same sintax as the current sxw for rml->pdf report engine. 2) When called, the odt->odt engine should interpret the fields description and insert the data in the odt template, as the rml->pdf engine does for rml. 3) The resulting data is opened by openoffice.org. 4) The new odt->odt engine should be integrated with the new (and not released) Tiny report plugin for openoffice. 5) [ADDED] The new engine should be fail-proof: if the report is wrongly formatted or data is missing, it should not crash, but tell the user what happened... This way the user can fully use the formatting power of openoffice.org. I am not a professional programmer. So you will probably notice some aspects of my "hobbist" description. But I can struggle to find some resources to push the development of TinyERP. That's what counts. Best regards, Emanuele Gissi. --- http://gissi.free.fr _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
