[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782960#comment-13782960
]
Vincent Hennebert commented on FOP-2293:
----------------------------------------
{quote}
(3) the suggested extension on multi-switch retains and precisely uses the
intended semantics of multi-switch: to select between alternatives;
{quote}
I understand the semantics of multi-switch to be listing alternatives; the
_selection_ of alternatives is left to fo:multi-toggle.
{quote}
(4) the specification does not preclude using a alternate selection mechanism
than multi-toggle or using such a mechanism to imply semantics similar to
multi-toggle;
{quote}
Exactly; which is why I propose this fox:dynamic-content element.
{quote}
(5) resorting to defining a new element which almost completely overlaps the
semantics of an existing element is architecturally unsound, and leads to
proliferation of variation rather than harmonization of use;
{quote}
I don't see what the overlap would be between fo:multi-switch and
fox:dynamic-content?
In fact, fo:multi-switch could be put as a child of fox:dynamic-content:
{code:xml}
<fox:dynamic-content fitting-strategy="best-fit">
<fo:multi-switch>
<fo:multi-case starting-state="hide">
<fo:block>Case 1</fo:block>
</fo:multi-case>
<fo:multi-case starting-state="hide">
<fo:block>Case 2</fo:block>
</fo:multi-case>
</fo:multi-switch>
</fox:dynamic-content>
{code}
That said, I don't care too much whether the functionality is implemented as an
extension element or property. The ease with which either possibility can be
implemented also counts.
Vincent
> 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)
