This is the documentation home page for the Pentaho Reporting space.
Documentation for the Classic-Engine Design-Tools
Pentaho Reporting Classic Engine (JFreeReport 0.8)
The Pentaho Reporting Classic Engine is the proven and stable branch of our embedded reporting engine. It is a banded reporting engine that is based on an absolute layout. Our plan is to evolve this engine into 'Pentaho Reporting 1.0'.
Developer Guides
- Classic Engine How-To Docs
- Dependency documentation
- Developer's Getting Started Guide
- Pentaho Reporting's Modular Design
- Using the DocumentBundle Reader and Writer
- Parameter Definitions
- Report Processing State Diagramm
Installation Guides
User Guides
- Classic Engine Algorithm
- Advanced Reporting Guide
- Pentaho Reporting XML Definition formats
- Layout Restictions for Table-based and Plain-Text output
- Report XML Definition DTD/XSD

- Shortcut: Formula Syntax
Pentaho Reporting Flow Engine (JFreeReport 0.9)
The Pentaho Reporting Flow Engine is the next generation reporting engine for the Pentaho Project. As we are still adding features to the engine to get a complete first version of this thing, this is the right time to collect ideas and feature-requests to make the Engine the best Reporting Engine on this planet.This part of the Wiki itself is subdivided into three sections. The Flow-Engine will evolve into 'Pentaho Reporting 2.0'.
Documentation
The documentation section acts as general library. It contains the content for the manual and all how-to's and technical articles that have been or will be written. Before posting an feature request, peek in here to see whether your requested feature isn't already implemented.
To-Do List
The To-Do list contains all tasks, that have been already scheduled for a later (or possibly the next) release.
Feature Requests
Please enter these requests into our JIRA system
. The Wish-List contains all (and I mean it: all) ideas, features and usage scenarios that could be possibly done using JFreeReport. Except for doing the Dishes or Time-Travelling, any idea is welcome here.
Once the idea has been developed enough, it will move on the To-Do list.
If the idea is already implemented, it moves into the documentation section - either as Documentation-ToDo or as link to the manual.
If the idea is rejected (for instance if it is not solveable, or is not even remotely related to reporting or content processing), it ends up in the [Recycle Bin].