TODO List for FOP


	FOP TODO

Core Features - these are the areas that are important to getting fop to be useable for general use.

Processing improvements - these are mainly things that can be improved in the way fop works, eg. resources usage, pdf output etc.

Enhancements - these are added functionality that might be useful, no comment is made about the suitability of these suggestions.


	Core Features


	Layout

This is the crucial part to getting FOP to make it to the next step.


	Webstart Demo

a demo using Java Webstart that runs the awt viewer and supports linking from an index


	Website

Need to improve the website to better demonstrate what fop is and can do. Examples, screenshots, pdf documents.


	Property Support

Currently all properties are in the xml file. We need to handle all default values properly (including ones that change depending on the element) and all possible values.

To see if a property is implemented then look in the src/codegen/foproperties.xml file.

To see if a particular element uses this property then look in the element code. This is generally found in the package org.apache.fop.fo.flow.*.


	Property Resolution

This is support for the functions in property values that evaluate some expression. Better support for resolution including support for "inherit" and values with lists.


	Validity Checking

Check the validity of children for a particular element to ensure there are no invalid children. Should help process the layout better.


	Processing Improvements


	Logging

Support for proper logging with logKit.


	Image Handling

Needs to be a bit more solid and allow for direct insertion of images (jpeg) into the pdf.


	Configuration

Support for avalon. Better multithread handling.


	More PDF Outputs

Support for streaming and linearized pdf to help with different deployement of pdf documents.


	i18n in awt viewer

Use proper i18n handling for awt viewer.


	better abstraction of rendering classes

put all common rendering processes into an abstract class that has no dependancies on any specific renderers.


	Enhancements


	linking support in svg

support the a link rendering for the svg output.


	input from url

be able to specify a url as the input fo (or xml, xsl) documents.


	improve text handling in svg

support (better) the direct rendering of text into pdf graphics and other similair outputs


	svg renderer (output to svg doc for slide presentation)

Create an SVGRenderer that will render all pages onto a single svg document suitable for slide show presentations (with batik) suggested by Vincent Hardy.


	stream encoding

Support for different encoding on different types of streams in pdf document. For example images.


	svg features

currently patterns and gradients are not generated properly