Glenn Adams commented on FOP-2293:

I've added a question at [1] as follows:

"Instead of creating new extension element types, why not use fo:multi-switch 
and fo:multi-case (instead of the proposed fox:best-fit and 
fox:best-fit-alternative), along with a new extension property, fox:best-fit on 
fo:multi-switch, which triggers an implicit process for setting the 
currently-visible-multi-case trait on the fo:multi-switch to select none or one 
of the alternative fo:multi-case sub-trees to contribute generated areas? The 
structure and function of these existing FO element types exactly match the 
proposed new element types. [GA]"

[1] https://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement
> Whitespace management extension
> -------------------------------
>                 Key: FOP-2293
>                 URL: https://issues.apache.org/jira/browse/FOP-2293
>             Project: Fop
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>              Labels: XSL-FO
>             Fix For: trunk
>         Attachments: bestfit.fo, doc.pdf, multiple-feasible-nodes.fo, 
> patch.patch, patch-rev1.1.patch, patch-rev1.patch
> I have been working on an extension for whitespace management, similar to 
> what's described here: 
> http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement
> The logic of the extension is very simple: the user defines a set of 
> alternatives that he wishes to insert at the end of a page, then if there is 
> enough space left, FOP will pick the alternative that best matches the user's 
> selection criteria (first fit, smallest fit, biggest fit).
> This is my first work on FOP and it took me almost 2 months to reach this 
> stage in development. But it's not the end of course, so I'm relying on your 
> feedback to improve it.
> Thank you

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to