Pascal Sancho commented on FOP-2293:
Despite of different interpretations of REC, in fine we have 2 alternatives to
define the toggle mechanic:
- use only fox attributes
- use fox element.
>From userland, the attribute based approach seems more appropriate:
- replace all fo:multi-toggle with only one fox attribute
- at a glance, the user can understand what is the present role the
- all fox material is in the same location, and fox overload is minimal.
Internally, I've not investigated to know what approach is the best one.
I definitively prefer the only-attribute approach, but I will follow the
general consensus (if any...)
> 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:
> 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