[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seifeddine Dridi updated FOP-2293:
----------------------------------
Attachment: FO_multi-switch_with_best-fit_extension.patch
_Changelog_
* Added a basic implementation of FO multi-switch.
* Added new extension properties (fox:auto-toggle and fox:fitting-strategy) to
FO multi-switch, which enable different handling of the set of mutli-case(s).
* New fitting strategy (any) added to best-fit; it loops over the mutli-case(s)
and inserts any alternative that can be fitted inside the current page.
* Moved the core logic of the best-fit extension to PageBreakingAlgorithm, as
suggested by Vincent.
_Current issues_
* Inserting inline content inside an FO multi-case makes FOP crash. This is
because any inline tag should be wrapped inside a block-level container. The
solution that I found so far, is that once the currently visible multi-case is
known, we can insert it as a child of the parent of the FO multi-switch and
remove the multi-switch altogether. But this doesn't work in case the best-fit
extension is enabled.
* The extension does not yet support changing page IPD.
> 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_test.fo,
> FO_multi-switch_with_best-fit_extension.patch, 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)
