I don't know why birt is integrated with Ofbiz. A reporting tools, is an add-on to any database driven system, and not essential for the over all functionality. Yes all of us need reports, and most of the time we use a reporting engine, but why can't it be separated from the code base, and used as a separate application ?
>From my perspective, the core should contain only components needed to bring it up to a functional state. Entity Engine, Service Engine, fall under this category. Some may argue that UI should be considered as well, and this is valid argument. But when it comes to reporting engine, I don't think so. On Thu, Mar 22, 2012 at 7:43 AM, Erwan de FERRIERES <erwan.de-ferrie...@nereide.fr> wrote: > Le 22/03/2012 02:38, Hans Bakker a écrit : > >> Jacopo, >> >> you are making here a very negative review of the Birt integration....as >> any component sure there is room for improvement however.... >> >> Some positives you did not even notice? >> >> 1. can use minilanguage for the retrieval >> 2. can use ofbiz fieldnames and entity names. (not databasenames) >> 3. can use OFBiz views..... >> 4. can fully integrate in the ERP application. >> 5. has many inbuilt output formats. >> 6. Incorporates the warehouse entities. >> >> Created/extended the datawarehouse which is essential for ordereporting. >> We have very big customers where using order reports directly on the >> OFBiz database was not possible. >> >> This warehouse function is essential for large customers >> >> I very strongly think about keeping this in the framework. >> >> BI component I agree, can go.... >> >> Regards, >> Hans >> >> > > I'm in two minds about BIRT. It's a fine tool to make reports, but underused > in OFBiz. > If the concerns Jacopo has about it were resolved, will it be kept in > framework ? > Also, creating more of those reports (with not available features in FOP), > will this go in the right way to keep it there ? > > > -- > Erwan de FERRIERES > www.nereide.biz
