Andreas L. Delmelle updated FOP-2469:
New patch, with some further minor changes here and there, and the three
additional test cases added to the layout engine test suite.
Removed the isAutoLayout() method from AbstractBaseLM and LayoutManager, and
made the implementations package private in TableLM and TableCellLM.
I experimented with having the default implementation in AbstractBaseLM return
false, which ultimately produces the exact same output, so I was left wondering
what purpose the isAutoLayout() calls in BlockStackingLM and LineLM have other
than avoiding some warning messages in the log, which seems to be the only
difference ( ? )
That could also be avoided by passing the LayoutContext to the
updateContentArea...() method, which is what I did instead.
> [PATCH] auto table layout
> Key: FOP-2469
> URL: https://issues.apache.org/jira/browse/FOP-2469
> Project: FOP
> Issue Type: Bug
> Components: layout/unqualified
> Affects Versions: trunk
> Environment: Windows 7, JDK 7
> Reporter: Gregor Berg
> Assignee: Andreas L. Delmelle
> Fix For: trunk
> Attachments: 2015-05-13-auto-table-layout.patch,
> 2015-06-09-LM-to-LC-refactoring-update.patch, FOP-2469_20150621.patch,
> FOP2469-auto-table-layout.xml, resize-all-but-static-spanned-columns.xml,
> resize-spanned-columns.xml, warning-only-static-columns-are-spanned.xml
> this is a patch which enables table-layout=auto. It is quite robust, it can
> not only handle linebreaks and pagebreaks, but it also copes with auto tables
> in fixed tables in auto tables.
> Essentially, it is the patch of issue FOP-2450 adapted to the trunk version
> of FOP.
> Best regards,
This message was sent by Atlassian JIRA