it has been a little while since I last contributed on BIRT-exchange. The reasons behind it are quite simply a combinaison of other project commitments and my recent work on dashbirt, which I am hoping will make up for my absence.
So what exactly is dashbirt?
DashBIRT is a web application built upon the BIRT Chart Engine API and AJAX technology to enable charts (rendered to the browser in SVG format) to interact with one another, through the invocation of scripts.
This DashBIRT demo contains a sample jsp page (see included screenshot), which renders the following charts, built with the RCP Report Designer 2.5.1:
- top selling models (pie chart),
- sales by customer (bar chart).
Interactivity on click of each slice of the top selling models pie chart has been enabled to fire the changeProduct client-side event, providing the product name as an argument.
The sales by customer bar chart has been configured to subscribe to this event.
Feel free to download this dev share and to add your own charts, querying your own database, rather than the classic models sample database.
Future of DashBIRT
This is where you can contribute ;-)
Once you've tested dashbirt, you will probably find some limitations.
First of all, the data set evaluator used to populate the chart is quite primitive, so using expressions rather than direct column binding will most likely not work. If anyone wishes to suggest how to improve the evaluator provided or contribute a less primitive one, let me know!
Secondly, I've only tested simple pie and bar charts, and would be interested to find out if this functionality still stands the test with other chart types. Again, please let me know if you find any odd behaviours.
Thirdly, it only supports charts at the moment, but I can see how other report elements might also need to be "controlled", to allow more dynamic reports, showing multiple tables/crosstabs.
Finally, this prototype does not support event bubbling, for instance where chart c subscribes to an event generated by chart b, itself subscribed to an event from chart a. In this instance, only chart b gets refreshed, where you would logically expect chart c to also get updated. The reason why I chose not to support this feature is "e;what parameter values would you pass from chart b?"e; You would expect the 1st value in chart b to be selected, but this might be difficult to implement. I will be eagerly awaiting any suggestions,
Happy BIRTing,
Regards,
Cedric
Attached File(s)
-
dashbirt.jpg (42.75K)
Number of downloads: 18 -
dashbirt.jpg (42.75K)
Number of downloads: 18



MultiQuote




