[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
On Tuesday 20 May 2003 11:14 am, Paul Weaver wrote: > >Tables should be avoided at all times. Especially regarding layout. Not strictly. Tables do have a place - a place about the same size as frames - technical documents that display data that requires more than one COLUMN (note: not rows, >1 column.) I'm in the process of implementing this for the www.dclug.org.uk site which currently uses tables for presentation but not for much longer. (As part of upgrading from HTML4 Transitional to HTML4.01 Strict.) > No, tables should be avoided regarding layout. If I have a piece of Tables currently used for layout are deprecated and need to be replaced by CSS - it does work and you'll be hard pressed to tell just when the DCLUG site has been updated. I've got a validation image to put on a few main pages to indicate when it's complete. I'm away for a few weeks so it'll be end of June now. > information in a tabulated format (say part of a CSV file), what better way > then to tabulate it? Some cells might be links too. > > Whats wrong with a table like this? > > Header: Name/Age/Picutre/homepage > Data: Bob/45/<img>/www.bob.com > Data: Mary/85/<img>/www.mary.com > Data: Jim/19/<img>/www.jim.com It's OK. Make sure you follow the W3C recommendation and put the Header Name Age Picture homepage titles in <th> tags. Remember also that <td align=center> etc. is also deprecated. > > > > -- > The Mailing List for the Devon & Cornwall LUG > Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the > message body to unsubscribe. -- Neil Williams ============= http://www.codehelp.co.uk http://www.dclug.org.uk http://www.wewantbroadband.co.uk/
Attachment:
pgp00015.pgp
Description: signature