DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
------- Additional Comments From [EMAIL PROTECTED] 2006-08-17 17:59 -------
(In reply to comment #7)
> We could quite easily keep track of the maximum number of cells in a
> row as the FOTree is built, so that, by the time layout starts, the
> layoutmanager could already know what the maximum column-
> count will be for the whole table without having to iterate over all the rows.
To expand a bit more upon this (could also be of use for fixed-layout):
Ideally, ColumnSetup should be made to deal with both implicit and explicit
columns completely, so the
TableContentLM does not need to sort this stuff out. The columns in ColumnSetup
should be the table-
I did wonder whether this should be viewed on a per-page basis...? I mean: say
you have a table with
five cells per row (100+ rows), except for the last row which has six.
Do we layout the whole table as if there were six columns, or only the last
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.