| BIRT 2.0 Features - in or out?? [message #98893] |
Tue, 13 December 2005 14:27  |
Eclipse User |
|
|
|
Originally posted by: mlorenz.nc.rr.com
The BIRT 2.0 release page lists a number of features. So many, that I
assume not everything is included. So...here is my "key" list that I
really need. I'm sure others have variations galore. My question - which
of these will be in the final 2.0 release? (all of these are copied
directly from the BIRT 2.0 page and I'm looking for more than "Yes" if
only partial functionality is to be supported)
* Report Paging: Long reports need to be divided into pages for effective
use. This division can occur either automatically, or with specific page
breaks determined by the report developer. Multi-page report support will
allow the report developer to design reports that have controlled page
breaks (such as for each new group value), or using automatic page breaks,
and for the application developer to integrate page navigation of BIRT
reports into the application itself.
* Robust PDF generation is a key component for reporting since many users
generate PDF versions of the report for portability, printing and
distribution. For BIRT, the PDF support needs to be very high quality.
This project addresses issues related to PDF generation using FOP such as
slow performance, limited support for lines and borders, and others.
* This project looks at the charting component of BIRT to make a number of
significant improvements in chart specification and generation.
* Persistent Storage of Report Output: It is often desirable to run a
report and then store the results of that report for viewing later. ... To
support this scenario, this project extends BIRT to offer a way to
persistently save a report for viewing at some point in the future.
|
|
|
| Re: BIRT 2.0 Features - in or out?? [message #99119 is a reply to message #98893] |
Wed, 14 December 2005 12:26  |
| Eclipse User |
|
|
|
Mark,
The project plan that is posted on the site
( http://www.eclipse.org/birt/index.php?page=project/project_p lan_R2_0_0_Draft.html)
is accurate. In fact, we just reviewed it last week and updated it with
a few additional projects that were not listed in the previous version.
All the features you list below will be included in the final release,
but not all are in M3 (see the M3 New and Notable for details). In
particular, the Report Paging feature is not in M3.
Enjoy! and let us know what you think.
Paul.
BIRT PMC
Mark Lorenz wrote:
> The BIRT 2.0 release page lists a number of features. So many, that I
> assume not everything is included. So...here is my "key" list that I
> really need. I'm sure others have variations galore. My question -
> which of these will be in the final 2.0 release? (all of these are
> copied directly from the BIRT 2.0 page and I'm looking for more than
> "Yes" if only partial functionality is to be supported)
>
> * Report Paging: Long reports need to be divided into pages for
> effective use. This division can occur either automatically, or with
> specific page breaks determined by the report developer. Multi-page
> report support will allow the report developer to design reports that
> have controlled page breaks (such as for each new group value), or using
> automatic page breaks, and for the application developer to integrate
> page navigation of BIRT reports into the application itself.
>
> * Robust PDF generation is a key component for reporting since many
> users generate PDF versions of the report for portability, printing and
> distribution. For BIRT, the PDF support needs to be very high quality.
> This project addresses issues related to PDF generation using FOP such
> as slow performance, limited support for lines and borders, and others.
>
> * This project looks at the charting component of BIRT to make a number
> of significant improvements in chart specification and generation.
>
> * Persistent Storage of Report Output: It is often desirable to run a
> report and then store the results of that report for viewing later. ...
> To support this scenario, this project extends BIRT to offer a way to
> persistently save a report for viewing at some point in the future.
>
|
|
|
Powered by
FUDForum. Page generated in 0.06363 seconds
Home