Dear Pedro, I'm in favor of you to create the LP project if you would like.
Thanks a lot ! On Mon, Oct 28, 2013 at 6:34 PM, Pedro Manuel Baeza Romero < pedro.ba...@gmail.com> wrote: > I vote for this approach for both questions! > > Tell me if you want me to do the "dirty part" (launchpad management and so > on). > > Regards. > > > 2013/10/28 Joël Grand-Guillaume <joel.grandguilla...@camptocamp.com> > >> Dear all, >> >> >> May be not mixing all things in this thread. @Pedro, I'm in favor of >> creating a projects for all report engines, like you suggested : >> openerp-report-engines => put in here the pentaho work by WillowIT, the >> birt report suggested here and may be others. The invoice_report, >> sale_report and so on can be used for the report in there-self. >> >> Who vote for this ? >> >> Second, as suggested by Raphaël, could be great to have a place where to >> get easier access to properties in SQL into some generic) base module. I >> vote also for server-env-tool, who else ? >> >> Thanks for the work ! >> >> Regards, >> >> Joël >> >> >> >> >> >> >> On Fri, Oct 25, 2013 at 12:11 AM, Raphael Valyi <rva...@gmail.com> wrote: >> >>> Hello, >>> >>> I would like to see work to extract the tools that Christophe Chauvet >>> from Syleam made for Penthao to get easier access to properties in SQL into >>> some generic (server-tool branch?) base module >>> >>> https://github.com/syleam/openerp-pdi-connector/tree/master/pdi_connector/sql >>> >>> I think all reporting technologies that access the database directly >>> could benefit from such tools and they lack badly today. Accessing via the >>> ORM is cool, but it's not always the solution when you need performance and >>> compatibility. >>> >>> What do you think? >>> >>> Regard. >>> >>> >>> -- >>> Raphaël Valyi >>> Founder and consultant >>> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> >>> +55 21 2516 2954 >>> www.akretion.com >>> >>> >>> >>> >>> On Thu, Oct 24, 2013 at 6:42 AM, Pedro Manuel Baeza Romero < >>> pedro.ba...@gmail.com> wrote: >>> >>>> Hi, Phui, >>>> >>>> Thank you very much for your efforts. We haven't decide yet how to >>>> organise the report-engines modules (one repository for all - my bet - or >>>> one for each report-engine), but I think it's pretty clear that reports for >>>> each area will be on specific repositories for this topic (invoice_report, >>>> sale_report and so on). For now, your repository is a good start to collect >>>> all and beta testing. >>>> >>>> Regards. >>>> >>>> >>>> >>>> 2013/10/24 Phui Hock <phuih...@gmail.com> >>>> >>>>> Hi again, >>>>> I have just pushed all my stuff onto >>>>> https://launchpad.net/openerp-report-birt and wrote a bit about it in >>>>> README.md, with steps to install the modules and Tomcat. >>>>> >>>>> Here is a few screenshots what to expect: >>>>> http://ypix.me/fHdh/ >>>>> >>>>> >>>>> -- PH >>>>> >>>>> >>>>> On Thu, Oct 24, 2013 at 1:18 AM, Phui Hock <phuih...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> I've created a project at https://launchpad.net/openerp-report-birt and >>>>>> am in the midst of cleaning up of bits of code and the example reports. I >>>>>> can only start documenting what I've done and how to set it up like.. >>>>>> tomorrow, since it's quite late over here. >>>>>> >>>>>> I have the project structure that looks like this: >>>>>> >>>>>> trunk/ >>>>>> __openerp__.py >>>>>> .... >>>>>> ./examples/report_birt_sale/__openerp__.py >>>>>> ./examples/report_birt_sale/rpt/sale_order.rptdesign >>>>>> ./examples/report_birt_account/__openerp__.py >>>>>> ./examples/report_birt_account/account_invoice.rptdesign >>>>>> ... >>>>>> >>>>>> I don't plan to create individual project for each report since I >>>>>> foresee they need to be changed/adapted for any company. So they are >>>>>> there >>>>>> only for reference. >>>>>> >>>>>> Question is, is openerp-reporting going to be project group, or a >>>>>> shared repo? >>>>>> >>>>>> >>>>>> -- PH >>>>>> >>>>>> >>>>>> On Thu, Oct 24, 2013 at 12:47 AM, Pedro Manuel Baeza Romero < >>>>>> pedro.ba...@gmail.com> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> In this >>>>>>> MP<https://code.launchpad.net/~luc-demeyer/server-env-tools/7.0-report_xls/+merge/192242>, >>>>>>> it has arisen again the question about creating a new >>>>>>> repository/repositories for reporting engines. I bet for a single >>>>>>> repository called openerp-reporting or openerp-report-engines, with >>>>>>> these >>>>>>> modules inside (report_birt, report_xls, etc). >>>>>>> >>>>>>> What do you think? >>>>>>> >>>>>>> Regards. >>>>>>> >>>>>>> >>>>>>> 2013/10/22 Maxime Chambreuil <maxime.chambre...@savoirfairelinux.com >>>>>>> > >>>>>>> >>>>>>>> +1 for http://launchpad.net/openerp-birt >>>>>>>> >>>>>>>> We would be more than happy to contribute. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> -- >>>>>>>> Maxime Chambreuil >>>>>>>> +1 (514) 276-5468 #126 >>>>>>>> >>>>>>>> ------------------------------ >>>>>>>> Hi, >>>>>>>> I am wondering if there is any interest in Eclipse BIRT-based >>>>>>>> reports for OpenERP. I wrote a simple reporting module, which is >>>>>>>> essential >>>>>>>> a proxy to external BIRT server to generate PDF. >>>>>>>> >>>>>>>> The module is partly inspired by >>>>>>>> https://github.com/vaab/report_birt, but with minor tweaks and >>>>>>>> example reports. This module does not require additional columns to be >>>>>>>> created. >>>>>>>> >>>>>>>> Examples of "Quotation / Sale Order" and "Invoice" reports can also >>>>>>>> be found and installed as separate modules. All of them are currently >>>>>>>> hosted at https://code.launchpad.net/~phuihock >>>>>>>> >>>>>>>> -- PH >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> 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 >>> >>> >> >> >> -- >> >> >> *camptocamp* >> INNOVATIVE SOLUTIONS >> BY OPEN SOURCE EXPERTS >> >> *Joël Grand-Guillaume* >> Division Manager >> Business Solutions >> >> +41 21 619 10 28 >> www.camptocamp.com >> >> >> > -- *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Joël Grand-Guillaume* Division Manager Business Solutions +41 21 619 10 28 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
