| 1 |
> Also, see how I'm doing the news items with divs instead of |
| 2 |
> tables? The |
| 3 |
> use of tables should be limited to tabular data unless |
| 4 |
> necessary. If you |
| 5 |
> want to play around with what I have there now try to stick |
| 6 |
> with divs. |
| 7 |
> If you we can't figure out how to make it acceptable that way we can |
| 8 |
> revert to tables as a last resort. |
| 9 |
|
| 10 |
I would say that since tables are used to display relationships in data and |
| 11 |
there are relationships in our news table (horizontally: in a row the |
| 12 |
date/author is related to the news posting and together this is one |
| 13 |
instance; vertically: column of date/author, column of news postings), it |
| 14 |
makes some sense to use tables provided that the posting is only a short |
| 15 |
abstract i.e. a few lines long. |
| 16 |
|
| 17 |
Divs would work, but not sure if it structurally makes sense. If using |
| 18 |
divs, we'd have to set it up like a table to get the vertical alignments |
| 19 |
correctly. One div per news item as a container, then date/author in one |
| 20 |
div floated to the left (width specified value, so we don't get the |
| 21 |
horizontal white gap in between this and the abstract) and news posting in |
| 22 |
another div floated to the right (width auto). Have not tried this but it |
| 23 |
could work. If anything funny happens e.g. the news items containers |
| 24 |
overlap, the style="clear:both" br may need to be used. |
| 25 |
|
| 26 |
Aaron |
| 27 |
|
| 28 |
-- |
| 29 |
www-redesign@g.o mailing list |
Archives