If I'm reading you right, your complaint is that VALIGN requires two passes
through the table to do the pagination. I believe you're right. But I
would argue that you should probably do two passes through it anyway: How
do you decide the width of each column, if some of the cells contain text
that is too long to fit without wrapping? You need to scale down the
widths of the columns in some way, and then wrap the too-long text. In
order to keep the tables "looking nice", this scaling down is weighted
differently for each column, more or less according to the difference
between the smallest possible width of the column, and the "desired" width
of the column. Those that differ the most (i.e., those that have
exceptionally "wide" cells -- before wrapping that is) get scaled down the
most. In order to figure out the scaling factor for a column, you have to
go through the entire table, before you can do any output.
>The last time I looked at the table support in XMosaic, it was in pretty sad
>shape. It did not even conform fully to the HTML+ model, to say nothing of the
>HTML3 model. Perhaps it has been improved since then.
This is still true (in released versions, beta or otherwise), but it is
second on the priority list for work on the X platform at the moment (CCI
is first).
mag
-- Tom Magliery ** NCSA ** 605 E Springfield ** Champaign IL 61820 ** USA