Understanding the BIRT APIs : About the BIRT Chart Engine API : Chart engine class hierarchy
 
Chart engine class hierarchy
The diagrams that follow contain hierarchies for the following chart engine packages:
*org.eclipse.birt.chart.aggregate
*org.eclipse.birt.chart.model.attribute
*org.eclipse.birt.chart.datafeed
*org.eclipse.birt.chart.model.component
*org.eclipse.birt.chart.device
*org.eclipse.birt.chart.model.data
*org.eclipse.birt.chart.event
*org.eclipse.birt.chart.model.layout
*org.eclipse.birt.chart.exception
*org.eclipse.birt.chart.model.type
*org.eclipse.birt.chart.factory
*org.eclipse.birt.chart.render
*org.eclipse.birt.chart.log
*org.eclipse.birt.chart.script
*org.eclipse.birt.chart.model
*org.eclipse.birt.chart.util
The hierarchy diagrams for the org.eclipse.birt.chart.model.*.impl packages are not included because they are simply implementations of the interfaces in the corresponding org.eclipse.birt.chart.model.* packages. The model packages, with two exceptions, contain only interfaces.
The first exception is org.eclipse.birt.chart.model, which has one class, ScriptHandler. The second exception is org.eclipse.birt.chart.model.attribute, which has a set of enumeration classes, one for each attribute. Each of the enumeration classes contains only a list of valid values for its attribute.