Introduction

The goal of this project is to deliver a rich, thin client interface for designing Pentaho Dashboards. This interface will provide users with the ability to create rich, interactive dashboards by combining Pentaho charts, reports, common POV controls and external content.

This project will be managed as an Pentaho incubation project making it very easy for you to contribute in nearly any phase or aspect of the development lifecycle.  For more information about the Incubation process, please visit Incubation Home in the Community section of the Pentaho Wiki.

Screenshots and Recorded Demo

the attachement could not be retrieved! Recorded Demo

Screenshot

Screenshot

The screenshots and screencast above are taken of the Pentaho Dashboard Designer Protoype used to prove the feasibility of developing a 100% thin client Dashboard Design interface.

Project Summary 

Note: We are actively recruiting a working group for the Pentaho Dashboard Designer.  The activities of the working group includes includes regular, active participation in some or all of the following:

• Review of requirements proposals, architectural designs, product specifications, etc.
• Actively participating in forum activity related the project
• Quality testing of any seed code, prototypes, and development builds
• Product development - documentation, training, bug fixes, seed code development, feature implementation, test suite, etc.

Conception Phase

The purpose of the conception phase is establish a structured environment for communicating ideas, brainstorming requirements, discussing use cases, evaluating any existing software, generate interest, etc. 

The goals of the Conception Phase of the incubation process are to:

1. Agree upon an initial set of high level requirements
2. Identify project stakeholders and establish a working group for the Conception and Seeding phases of incubation
3. Finalize requirements for moving the project on to the Seeding phase of incubation (including requirements for any seed code needed)

Requirements Proposal

The requirements proposal outlines a proposed set of requirements for delivering a full feature, 1.0 release of a Dashboard Designer product. 

See Pentaho Dashboard Designer 1.0 Proposal to review and comment on the proposal.

Architecture Proposal

The architecture needs to support several very difference deployment scenarios from template-based dashboards served by a standalone Pentaho server to highly customized or non-Java-based dashboard pages potentially mixing dashboard widgets with non-Pentaho content.  Any architecture which is a hybrid of the two above should be possible.  Each of these scenarios needs to permit widget selection (from a gallery of suitable action sequences) and ad-hoc metadata-based widget creation (using browser-based editing tools).

See Dashboard Designer Proposed Architecture for more information about these scenarios.

Dependencies

This section summarizes other software dependencies associated with the design and development of the the Pentaho Dashboard Designer.

 Other Links

• Activity Tracking - list of ongoing tasks and their owners
• Dashboard Designer Forum - live discussions around the Dashboard Designer incubation project
• Ingo Klose's Dashboard Framework Prototype and White Paper