Tasks

For an unique naming schema, these tasks need to be added as SourceForge-Tasks to get an unique ID. This ID should then be added to the page name, so that each case is trackable in the future. For the task-specific pages use the following naming schema:

"Task" + SourceforgeTaskID + SpeakingCamelCaseName

Reporting Engine (Classic)

These tasks need definitions in sourceforge:

[Add Kettle DataSources]
[Add XML+XPath DataSources]
[Add Userdefinable Formula Functions]
[Add SWT-equivalents for each Swing Dialog]

Reporting Engine (Flow)

[Create a Swing-Export GUI for Excel Exports]
[Create a Swing-Export GUI for HTML-Tables Exports]
[Create a Swing-Export GUI for Calc Exports]
[Create a Swing-Export GUI for RTF Exports]
[Create a Swing-Export GUI for PlainText Exports]
[Add Charting Support]
[Add Barcode Support]
[Add Kettle DataSources]
[Add XML+XPath DataSources]
[Add Userdefinable Formula Functions]
[Add SWT-equivalents for each Swing Dialog]

Reporting Web Viewer

[Create a Project]

LibLayout

Table-Export: Base modules need to be implemented
Table-Export: Create an Excel-Output target using POI
Table-Export: Create an HTML-Output target using HTML-Tables
Table-Export: Create an OpenOffice-Calc-Output target
[Document-Export: Create an RTF-Export]
[Document-Export: Create an Plain Text export]
[Add Table-Of-Contents]
[Add PDF-Outlines]
[Add Pass-Through-Nodes]
[Validate the HTML-Output]
[Add Float- and Absolute Positioning capabilities]
[Allow horizontal page spanning]

LibCharts

Collect the requirements for a meta-charting library

LibLoader

LibRepository

Write an Apache-VFS Plugin for LibRepository

LibFonts

Open Bugs

The status of all open Bugs for all projects is tracked in the Sourceforge Bug Tracker

Page Operations

Browse Space