From 02d11ee6f6ebbf942891b5a6d6c798bc371f3f2d Mon Sep 17 00:00:00 2001 From: Keiron Liddle Date: Tue, 22 May 2001 14:16:58 +0000 Subject: [PATCH] updated status for current situation, focus on redesign and testing git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@194268 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 131 +++++++++++++++++---------------------------------------- 1 file changed, 39 insertions(+), 92 deletions(-) diff --git a/STATUS b/STATUS index a8e7c57bf..6ba510128 100644 --- a/STATUS +++ b/STATUS @@ -14,106 +14,53 @@ Eric Schaeffer Jon Smirl - **** THINGS WORKED ON ***** -refactoring properties [Karen Lease] -region-start, region-end, writing-mode, tests [Arved Sandstrom] -upgrading svg (producing the dom in a new way and render that dom), -refactoring of line area (not immediately) [Keiron Liddle] -integrating Avalon and Fop [Steven Coffman] -docs, examples [Fotis Jannidis] +redesign/refactoring - layout [Karen Lease] +redesign/refactoring - page layout [Arved Sandstrom] +svg, testing [Keiron Liddle] **** THINGS TO DO **** -Support XSL Candidate Release - -first target is basic conformance - -1.One category of tasks will be to implement missing formatting objects. - -basic - fo:declarations - fo:multi-case - fo:table-and-caption - -extended - fo:bidi-override - fo:color-profile - fo:float - fo:initial-property-set - fo:inline-container - fo:marker - fo:multi-properties - fo:multi-property-set - fo:multi-switch - fo:multi-toggle - fo:region-end - fo:region-start - fo:retrieve-marker - fo:table-caption - fo:title - - -2. A not insignificant, category of tasks is to decide upon and - implement all reasonable properties required by the specification. This - also means that at this point, until further review, no FO can be considered - to be compliant. - This are the properties which must be implemented to reach basic conformance - - a) CHANGED - space-after.optimum (Incomplete) - space-before.optimum (Incomplete) - keep-with-next (Changed) - - b) NEW - alignment-adjust - alignment-baseline - baseline-shift - block-progression-dimension - border-after-precedence - border-before-precedence - border-end-precedence - border-start-precedence - clip - content-type - direction - display-align - dominant-baseline - font-variant - format - grouping-separator - grouping-size - inline-progression-dimension - keep-with-next - keep-with-previous - letter-value - line-stacking-strategy - number-columns-repeated - number-columns-spanned - number-rows-spanned - orphans - overflow - reference-orientation - relative-align - role - source-document - space-after (full) - space-before (full) - space-end - space-start - visibility - widows - writing-mode - z-index - -3. A third category of tasks is the ongoing effort to promote maintainability, - write more and better documentation, and to refine the build process. - a) add examples. In examples/fo there should be at least one file for each - supported flow object showing the use of all properties applying to it. +1) +The immediate list of things that need to be done. These include things +that may prevent other activity or could be done independantly. + +* Redesign of flow layout handling, breaks keeps, spacing etc. +* Redesign/factoring of line area handling. +* Testing system, moving old tests to new system etc. +* SVG +- integrating Avalon and Fop +- Documentation / website needs to better help users understand how to use FOP +- examples (a separate set of user fo examples) + +(* being worked on, - no current activity) + +2) +After the the layout handling is redesigned then these items should be +promoted to first priority. +These should be done with the aim of getting to basic conformance. + +- Implement all remaining formatting objects +- improve property handling for types not currently supported (eg. 'large' font) +- implement all required properties + +3) +Nail down external interfaces (the main part is fairly stable). +Setting base directory, using config, logging, extensions etc. + +Interfaces to include: +how does FOP get called +how does the formatter interface to renderers +how do people write new plug-ins: handlers for new image types +processors for fo:instream-foreign-object +4) +Improve the code. Follow the Sun Java coding guidelines. +Have better comments and correlation between spec terms +and methods etc. -- 2.39.5