Hi all, I have create a todo list. I will put this as part of the website (when I can) unless someone beats me to it. Currently it is only text, but will be xml when a suitable format presents itself. This should give some idea of main development concerns, general improvements and possible enhancements. It is probably not complete or totally correct but its a start. A number of things are already being worked on. ---------- Core Features - support all properties 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. - support all property functions This is support for the functions in property values that evaluate some expression. - support property resolution Better support for resolution including support for "inherit". - support all property reading in all elements Setup all elements so that they are reading the all (and only) the required properties. Including suitable abstraction and data structures for common groups of properties. - support all elements Support for the layout of all properties. - 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 - streaming support Support for the rendering of output as information becomes available rather than at the end. Should reduce amount of memory used and speed up in some ways. - image handling Needs to be a bit more solid and allow for direct insertion of images (jpeg) into the pdf. - support more pdf output formats Support for streaming and linearized pdf to help with different deployement of pdf documents. - configuration Support for avalon. Better multithread handling. - logging Support for proper multithread logging. - better data handling Better use of data structures, memory use. - 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 - request prop for url connections support for request headers for url connections (images) eg. cookies. - 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
