This means that any output format may be plugged in by writing a device extension.
A device refers to an implementation that translates rendering primitives into a specific file format.
It is probably the best choice over JPG and BMP as it supports transparency, 32 bits colors, and compression without loss. The rendering quality of text is also slightly better than SVG for small fonts, although this should be corrected in a future release.
The following table shows from which version each chart output format is supported in a BIRT report.
For instance SVG is supported in HTML reports since version 2.0.
The Chart package is included in the main BIRT distribution, but you can get it separately from the download page.
Select the BIRT version you need, and choose the Chart Engine distribution, it contains three folders: You can extract this into the Eclipse directory, it contains all chart plugins required to run, render and edit charts.
Note that nothing will appear inside Eclipse, those plugins are to be used by an application built on top of them.
This contains everything you need to create charting applications.
It includes all the runtime plugins, an example plugin, an examples view, a WTP extension (if you build a Web application using charts), documentation, and source code If you need to run your charting application outside Eclipse (web application or simple java application), this contains all the jars you need to put in your classpath.
You can also get the chart plugins directly from Git (birt), if you wish to get the latest source and the unit tests.
The following table summarizes the available chart types.
Internally, the charting engine writes to device independent primitives.