[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781803#comment-13781803
]
Pascal Sancho commented on FOP-2293:
------------------------------------
> I had a private discussion with Vincent and we agreed that
> it is best to implement FOX best-fit as a new element
> NOT a property of FO multi-switch. I'm still open to more suggestions, though.
Didn't know that. public debates should remain public...
I'm not convinced on why new fox element is better than new fox attribute.
See prepress extension, it only add new fox attributes.
And IMHO, as GA pointed it, multi-switch goals cover the needs of best-fit
extension; it just lakes some mechanism that extension should provide.
> In my opinion, best-fit is not the same as multi-toggle,
> the latter acts on a single multi-case while the former
> has to process the list of multi-case(s) at once,
> so it doesn't make much sense to put it into the switch-to property.
I agree on that, switch-to property should remain as what described in REC.
That why I propose the 2nd case: new fox property.
That said, the most important is to have a working extension, implementing it
in one or alternate way remains a background question.
WDYT?
> 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, FO_multi-switch.patch,
> FO_multi-switch_test.fo, multiple-feasible-nodes.fo, multi-switch_bestfit.fo,
> patch.patch, patch-rev1.1.patch, patch-rev1.patch, patch-rev2.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 was sent by Atlassian JIRA
(v6.1#6144)
