This is configurable,
and there could be any number of other statuses. While in an ideal world this is the
responsibility of the Data Managers to maintain, in the real world report developers'
efforts to push back usually result in nothing.
Conclusion
From the beginning: We familiarized ourselves with the Eclipse BIRT Design
Perspective. We familiarized ourselves with the various BIRT Report Components.
We build some simple reports, and some complex reports. We demonstrated how
re-use is possible through Libraries and Templates. We also saw some basic
report Scripting.
Hopefully, by reading this book you have gained a good fundamental understanding
about how BIRT works, and are now able to build BIRT reports. The BIRT
community is a growing one, and there are a number of resources out there for BIRT.
There is a growing user community on the Eclipse website. There are a few blogs
out there. There are a few developers of extensions for BIRT??”such as Tribix, which
makes output extensions.
Practical Example??”Building Reports for Bugzilla
[ 292 ]
BIRT is a large and difficult "animal" to define and comprehend. While on the surface
it seems that it is a report development platform, it is also a set of APIs that can be
consumed and extended to meet your needs. If the out-of-the-box output formats
aren't enough, then custom Emitters can be built.
Pages:
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232