Re: lynx-dev table formatting (possible) solution

[Rob Partington]

In message <address@hidden>, 
           address@hidden writes:
>  a little - we can make a two-pass renderer if someone figures out how
>  to manage the resulting information.

You don't strictly need a two pass renderer, though, do you?  Netscape
and IE both managed to render tables without them for a long time, afaik.

This is what the object tree thing is supposed to handle.  When you get
a table, say this one:

<table><tr><th>Item</th><th>Price</th></tr>
<tr><td>Fish</td><td>27.00</td></tr>
<tr><td>Children</td><td>14.00</td></tr>
</table>

That gets converted to an object tree like this (children -> that way):

TABLE-->TR-->TH-->"Item"
  |     +--->TH-->"Price"
  |
  +---->TR-->TD-->"Fish"
  |     +--->TD-->"27.00"
  |
  +---->TR-->TD-->"Children"
        +--->TD-->"14.00"
        
When you come to render this, you work out the size of the table cells
(by rendering them silently) and propagate them upwards to the rows 
and then the parent table before you actually start to render it.

At least, that's the theory.  I have the object tree bits, but not any
rendering code at the moment.

Comments?
-- 
rob partington / address@hidden