Re: Re: HTML_Table: thead, tfoot and tbody
| From: | Klaus Guenther | Date: | Mon, 01 Aug 2005 19:01:52 +0000 |
| Subject: | Re: Re: HTML_Table: thead, tfoot and tbody | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39101@lists.php.net to get a copy of this message | ||
On 8/1/2005 8:51 PM, Mark Wiesemann spake the following words:
>Klaus Guenther wrote:
>
>
>>+1 here, too :) I've been lurking, even if I haven't said anything on
>>the subject just yet. That sounds like a good implementation.
>>
>>
>I just started with the implementation. Here are the first two
>questions:
>
>(1) HTML_Table has the functions setRowType() and setColType(). One can
>set with them whether a row / a column should be rendered as <th> or
><td>. Should this influence the mapping to tbody/thead/tfoot? (E.g.: Row
>2 was set with setCellContents(), then $table->setRowType(2, 'TH') is
>called. Should row 2 now belong to thead or tbody?)
>
>
We need to keep 100% BC by default. There could be a switch that would
allow any th rows to be shifted to the header. By default we can leave
them like they are. Anyone else have a suggestion?
>(2) Is $_useTGroups an acceptable name for a class attribute? (I also
>want to use the array index 'tgroup' in $_structure to remember in which
>group the row belongs.)
>
>
Hmm... Let's keep separate row numbers for header, body, footer. That
way, you can assign things better, I think. Are there any problems with
that? Of course, it would (unfortunately) mean that if you change a row
from td to th and it gets shifted (see above), you'll get assigned a new
row id. As for the attribute name, I guess it is OK. Since it's going to
be private, it's not really such a big deal.
Klaus