
ok i have a geeky html type question... since there's been a few up here today.
is it right to love tables, and hate div's ?
what does current coding practice dictate regarding these elements ?
/always uses tables, never divs.
as for frames, well i see them as ok as long there's no scrollbars.
/hypocrite
edit: seems that there are still mixed opinions here. i think i'll try to make a div/css site and see if life gets any easier.
( , Fri 10 Sep 2004, 13:57, archived)

as long as it is consensual and you take appropriate precautions against venereal diseases and splinters
( , Fri 10 Sep 2004, 14:00, archived)

where a guy cums in this birds bumhole and she squeezes it into a cup and drinks it.
*goes and finds cup*
( , Fri 10 Sep 2004, 14:19, archived)

They confuse search engines (mildly, admittedly), require shitloads of code to do a very simple job, and require you to edit every page of a site if you want to change the layout.
There's more, but I can't be arsed. Tables should be used for displaying tabulated data, and not for laying out web pages.
This has been a public service announcement on behalf of the W3C
( , Fri 10 Sep 2004, 14:01, archived)

to be frank, if you desinged the site properly in the first place, you wouldn't need to change the layout.
( , Fri 10 Sep 2004, 14:09, archived)

and over 5-6 years you never ever want to change anything about the layout? Unlikely. What if you have a new product or service you want to add? Or a new dynamic feature? If it's in tables you probably have to scrap the lot.
Plus, all the format information has to load with every page instead of just cacheing from a CSS file once on your first hit.
( , Fri 10 Sep 2004, 14:13, archived)

and do you have bee in bonnet sydrome today sir
( , Fri 10 Sep 2004, 14:52, archived)

dont like you using tables
learnt that at uni dontcha know
you can tell because its such a pointless piece of information
( , Fri 10 Sep 2004, 14:02, archived)

and an important consideration if you're taking money off someone to design a site.
( , Fri 10 Sep 2004, 14:03, archived)

if you have shitloads of tables.
there's really no need to have any more than 4-5 tables on a page anyway.
/learnt that at college.
( , Fri 10 Sep 2004, 14:06, archived)

for laying out your page?
( , Fri 10 Sep 2004, 14:09, archived)

but strictly, do you mean that each part of the webpage would be enclosed in a DIV, and that each DIV part is assigned a class, then you use the CSS to specify the layout and properties of each class of DIV's ?
edit: how else would you split up the sections ?
( , Fri 10 Sep 2004, 14:19, archived)

look here: www.44media.com/whatwedo.html
which is controlled by this: www.44media.com/style.css
Not a table in sight. The source code is tiny.
( , Fri 10 Sep 2004, 14:21, archived)

but do give css a chance.
I'm currently learning with the aid of this tutorial: veerle.duoh.com/comments.php?id=208_0_2_10_C
which am nice for blog-stylee sites.
I'm rather please by how it's turning out.
( , Fri 10 Sep 2004, 14:23, archived)