The Pentaho Reporting Camp

Project news and updates directly from the source

Current Version: 3.6.1

Download Release Notes ChangeLog

Previous Version: 3.6.0

Download ChangeLog

Development Version: 3.7.0

Download Release Notes ChangeLog

What is Pentaho Reporting

Pentaho Reporting is a suite of open-source reporting tools which allows you to create relational and analytical reports from a wide range of data-sources.

 

The Pentaho Reporting Engine is able to create PDF, Excel, HTML, Text, Rich-Text-File and XML and CSV outputs of your data. Our OpenFormula/Excel-formula expressions help you to create more dynamic reports exactly the way you want them. Our open architecture and our powerful API and extension points make sure this system can grow with your requirements.

.. more ..

 

Subprojects and Project Structure

Wednesday, September 2, 2009

FusionCharts goes OpenSource - so Pentaho Reporting can go FusionCharts

With a rather silent Blog-entry, the FusionCharts team announced that FusionCharts Free will - from now on - be opensource. The code is dual licensed under the GPL v3 as well as under the MIT license. Thanks, FusionCharts and welcome as open-source citizen.This is a great move!



One of the goals of our Sugar-release will be to make the Web-experience of our reports a lot richer. For that, we plan to finally implement image-map support and to add built-in and easy-to-use Flash-Charting capabilities. With Citrus, we already have the technical base for it, as the attribute-expressions allow you to include any kind of HTML code into the output. But manual methods are cumbersome and prone to errors, so we can certainly do better. Originally, when FusionCharts was still closed-source, we had focused our plans solely on OpenFlashCharts as provider for more interactive charts. FusionCharts was barely on our radar at that time, as including closed-source parts into a open-source solution swiftly moves you into a strange legal limbo of when and how and how much you may or may not be able to distribute the closed-source parts and what may or may not constitute a legal use of this component. For that reason, we strictly limit our open-source software to open-source components.



(Yes, we could certainly use close-source components in the Enterprise-Edition parts of the application and would be able to work out some sensible license-agreements for all the components. But Enterprise-Edition/closed-source components get no community testing (so all the burden lies on our backs) and we get no contributions from outside of Pentaho. Therefore our development cycles for this stuff are much slower and more expensive than the cycles for the open-source code. From a pure developer's perspective, I won't shed a single tear if all closed-source code becomes open-source.)