Yes, but I haven't gotten to it yet. I'm not so sure at this point what it will rely on.
I think it's possible to do something better than just reporting.
If we could give users a good environment to deliver information, reports are not needed. If you have a good Analytical environment, users won't need a report.
A exploring tool, or better... a exploring framework is not being well covered by the open-source community. This would became in the OLAP world, and this is a good oportunity now as there is plenty of new specifications now. (See jolap at www.jcp.org)
You know... in the beggining users liked to have lots of reports.
Them we started to produce online systems. They don't need reports to transational system any more.
If we could have online analytical information, users wont need reporting. They would choose what information they want to see, and how they want to see it.
I'm sure there is space for a open-source framework like this.
Yeah right Clebert.. . The end user for these reports isn't a developer. You do realize most business are run off of MS Excel and Word! At the end of the day, I want to do more OLAPy data-cuby stuff, but at the same time...I want actual users.... that means printable formats will be a big part.
I think it's possible to create a MIX...
Allow the user naviage and customize the data before he prints the data.
Using dimensional data + filters on reports would allow users to do that.
(IMHO: That requires a Multi-Dimensional framework)
I agree with you that PrintFormats is a big part of our actual users. But if we could allow users to customize their reports before printing those techniques could get some power to the user.
That would be a good feature on reporting.
absolutely. If you're interested in kicking this off, I'll get my original design notes together, type them up and post them. However....We have to keep a perspective on what is 1.0 vs 2.0 vs 3.0 etc.
such a reporting/analyzing tool sounds great. I`ve developed a GUI for JasperReports a time ago. Good reporting engine. I'll keep an eye on this issue..
Not sure if this has already been identified - http://www.pentaho.org
Olap/mondrian support (with MDX and XML/A), ETL-kettle support, jasperreport engine and BIRT report engine, scheduling (via Quartz).