Return-Path: X-Original-To: apmail-ofbiz-dev-archive@www.apache.org Delivered-To: apmail-ofbiz-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97A35179D0 for ; Wed, 25 Mar 2015 10:46:05 +0000 (UTC) Received: (qmail 22314 invoked by uid 500); 25 Mar 2015 10:46:05 -0000 Delivered-To: apmail-ofbiz-dev-archive@ofbiz.apache.org Received: (qmail 22271 invoked by uid 500); 25 Mar 2015 10:46:05 -0000 Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list dev@ofbiz.apache.org Received: (qmail 22257 invoked by uid 99); 25 Mar 2015 10:46:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 10:46:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of slidingfilaments@gmail.com designates 209.85.215.54 as permitted sender) Received: from [209.85.215.54] (HELO mail-la0-f54.google.com) (209.85.215.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2015 10:45:40 +0000 Received: by labe2 with SMTP id e2so16129928lab.3 for ; Wed, 25 Mar 2015 03:44:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mSKurH7CRbsZSnBMb/veMN/nczEDxS1gxJEKvAdnXqE=; b=DIqy6JezJfo/tKwIpptufmvHWtH6g1MFeNHtZiFXibNoe7DxQHuXxWo4mF2BgfRPcI hdKU0aIAk+4IcwVrRsIRofppD8oa7BYn0EFv742v5CroWOACzlNl8Hd+EHmvW7CIHpt2 9Jz6jehWN5zGDUhyI9YR2IxIJr8MrhqPBF3sfPOiCKtMY01lzO1WWaxpVTJy4cYzNLMu BSy3MwnBHmnIYf0poil/Y36tbutSN2CTjNvxcZv6kPDt0WAjpGzSqf0xM086UlNBmEXX JITh75ogvMxn6ZS/NQ84fauRoZqimQtlJPYe4eYMH3+HNgVVKjsWjH2PZQa5Myc54K3P q+tw== MIME-Version: 1.0 X-Received: by 10.112.188.227 with SMTP id gd3mr8218246lbc.0.1427280248080; Wed, 25 Mar 2015 03:44:08 -0700 (PDT) Received: by 10.152.104.105 with HTTP; Wed, 25 Mar 2015 03:44:07 -0700 (PDT) In-Reply-To: References: <550EFB69.2060302@les7arts.com> <9EF8AAD3-4EB5-4ABE-8E38-88D45B6BBE0B@hotwaxsystems.com> <55116CF5.4080807@les7arts.com> <55117A9F.3090102@les7arts.com> <55117EC6.3070205@les7arts.com> <551180C3.4070308@les7arts.com> <09355682-CA32-4305-A629-249C7F59894D@hotwaxsystems.com> <5512860D.1030406@les7arts.com> Date: Wed, 25 Mar 2015 13:44:07 +0300 Message-ID: Subject: Re: [VOTE] reintroduce the evicted specialpurpose components in R13.07 From: Taher Alkhateeb To: dev@ofbiz.apache.org Content-Type: multipart/alternative; boundary=001a11c36aa82e8f1205121a9479 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c36aa82e8f1205121a9479 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Jacques, With respect to your question below on BIRT and regardless of whether reports are failing or not IMHO we should discuss the principles. So the question is very simple. Is it better to use Apache FOP with the screen widgets to create reports or is it better to utilize a reporting and business intelligence engine? To me, this is a no brainer. A full blown engine is definitely better (even if not necessarily BIRT) for the following reasons: 1- Designer WYSIWYG tools available for much greater productivity and user friendliness. You can even expose such tools directly to your clients. 2- Ability to design data set, cubes, parameters, charts, graphs, master pages with headers and footers, and a lot more 3- Ability to do dynamic scripting of the data on an event model which allows for maximum flexibility in design 4- Ability to export output to many formats (PDF, HTML, word, excel, CSV, ...) 5- Ability to specify unified report libraries containing shared themes, master pages, javascript source files, CSS, images, etc ... 6- Ability to deploy the reporting server as a standalone solution 7- Ability to integrate with the entity engine or to connect directly to the database. 8- Building reports on a modular design structure The above is just a quick brain dump, I am sure there are many other benefits. My 2 cents. Taher Alkhateeb On Wed, Mar 25, 2015 at 1:34 PM, Jacopo Cappellato < jacopo.cappellato@hotwaxsystems.com> wrote: > > On Mar 25, 2015, at 10:55 AM, Jacques Le Roux < > jacques.le.roux@les7arts.com> wrote: > > > Can we say that the Birt reports are better? Do they always work (I got > some issues there) > > No, I wouldn't say that (of course you are free to think otherwise, it is > just the *we* part that I disagree with). > > > > > Also just tried > http://demo-stable-ofbiz.apache.org/accounting/control/FinancialSummaryRe= portOptions?organizationPartyId=3DCompany > where Birt is not and all reports fail, normal? > > I am not sure I understand... I got the same errors with or without Birt: > the request maps are not defined; I don't see how this bug fits into this > conversation. > But for example, the balance sheet report: > > https://localhost:8443/accounting/control/BalanceSheet?organizationPartyI= d=3DCompany > is not a Birt report and works well; however the if you click on the > "Export as pdf" button you get an error when Birt is active while it work= s > when Birt is inactive. > > Jacopo > > > > > Jacques > > > > Le 24/03/2015 16:36, Jacopo Cappellato a =C3=A9crit : > >> The accounting component has financial reports implemented as screen > widgets (html/pdf/csv) that the Birt component overrides with different > ones implemented with Birt. > >> This is actually one example about a specialpurpose component that is > overriding/hiding functionality that is already provided by the > applications with a different one: you can't see them when Birt is enable= d. > >> > >> Jacopo > >> > >> On Mar 24, 2015, at 4:23 PM, Pierre Smits > wrote: > >> > >>> Don't we also have dependencies on birt? Regarding reporting in > accounting > >>> and order? > >>> > >>> Best regards, > >>> > >>> Pierre Smits > >> > >> > > --001a11c36aa82e8f1205121a9479--