Are Tables History?

T

Trevor

I read an array of comments signaling the end of TABLES, citing them
as old.

Can someone say what CSS code replaces something like the code below,
which I am using frequently?

Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

I don't know how CSS can replace this kind of structure, and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

CODE
====

<%@ Language=VBScript %>
<HTML>
<head>
<title>Redburg - Quality etailing</title>
<link rel="STYLESHEET" HREF="redburg.css">
</head>
<body>
<table width="100%" cellspacing="2" cellpadding="2">
<tr>
<td colspan="2" valign="top" align="center">
<!--#include virtual="/indexheader.asp"-->
<td>
<tr>
<td valign="top" align="center">
<!--#include virtual="/indexstoremenu.asp"-->
</td>
<td valign="top" align="center">
<!--#include virtual="/aboutredburgscreen.asp"-->
</td>
</tr>
</body>
</html>
 
W

William Tasso

Trevor said:
I read an array of comments signaling the end of TABLES, citing them
as old.

nope - tables are no longer (were they ever?) considered to be a useful
mechanism for defining page layout. There are still very much in use for
marking up tabular data.
Can someone say what CSS code replaces something like the code below,
which I am using frequently?

nope - not without a URL
Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

so what - there is nothing in that spec which requires tables for layout
I don't know how CSS can replace this kind of structure, and I would
like to know exactly what people are talking about when they say
TABLES are old hat.
...

stick around, publish a URL you will get the hang of it.
 
N

Nicolai P. Zwar

Trevor said:
I read an array of comments signaling the end of TABLES, citing them
as old.

Can someone say what CSS code replaces something like the code below,
which I am using frequently?

Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

I don't know how CSS can replace this kind of structure, and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

It's not at all that tables are "out", an "old hat", or no longer
useful. CSS cannot and is not supposed to replace tables where tables
are called for. But CSS is replacing tables where tables are solely used
for layouting.
CSS can easily replace the kind of structure in your small example if
the structure is one for design purposes.
Check http://www.csszengarden.com/ to see a few examples for pure CSS
layouts. You will find that a simple three or two column layout is a
piece of cake for CSS.
 
H

Hywel Jenkins

I read an array of comments signaling the end of TABLES, citing them
as old.

How would you display tabular data without tables? Someone suggested
the same thing as you a couple of weeks ago - it came across as an
extremely unreasoned ointp.
 
S

Sid Ismail

On 24 Sep 2003 10:35:34 -0700, (e-mail address removed) (Trevor) wrote:

: I read an array of comments signaling the end of TABLES, citing them
: as old.


Tables is not old, not will it ever be extinct. Perish the thought.

Hallelujah!

Sid
 
A

Adrienne

Gazing into my crystal ball I observed (e-mail address removed) (Trevor) writing
in
I read an array of comments signaling the end of TABLES, citing them
as old.

No, they are not old. They are to be used for tabular data, for instance,
a table containing products, prices and descriptions.
Can someone say what CSS code replaces something like the code below,
which I am using frequently?

See below.
Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

Nesting tables is a bad idea. Have you ever tried to navigate a table using
a speech browser? Open cell...cell table...open cell...
I don't know how CSS can replace this kind of structure, and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

See below.
CODE
====

<%@ Language=VBScript %>
<HTML>
<head>
<title>Redburg - Quality etailing</title>
<link rel="STYLESHEET" HREF="redburg.css"> </head> <body>
<table width="100%" cellspacing="2" cellpadding="2"> <tr>
<td colspan="2" valign="top" align="center">
<!--#include virtual="/indexheader.asp"--> <td> <tr>
<td valign="top" align="center">
<!--#include virtual="/indexstoremenu.asp"--> </td>
<td valign="top" align="center">
<!--#include virtual="/aboutredburgscreen.asp"--> </td> </tr> </body>
</html>

<%@ language=vbscript

dim whatever

%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"
"http://www.w3.org/TR/REC-html40/strict.dtd">
<html>
<head>
<title>Redburg - Quality etailing</title>
<link rel="STYLESHEET" HREF="redburg.css"> </head>
<body>
<div id="header">
<!-- #include virtual="/indexheader.asp" -->
</div>
<div id="storemenu">
<!-- #include virtual="/indexstoremenu.asp" -->
</div>
<div id="aboutredburg">
<!-- #include virtual="/aboutredburgscreen.asp" -->
</div>
</body>
</html>

Style divs according to taste, bake 20 minutes and serve.
 
M

Matthias Gutfeldt

Trevor said:
I read an array of comments signaling the end of TABLES, citing them
as old.

Trevor, we had this exact same topic just ten days ago, starting on
September 14, ending on September 17.

<http://groups.google.com/[email protected]>.

You even participated in the thread.

Are you suffering from amnesia, or is there something you really don't
understand about the difference between tables-based and css-based
layout?


Matthias
 
W

William Tasso

Matthias said:
...
or is there something you really don't
understand about the difference between tables-based and css-based
layout?

could be - I've noticed it's a difficult concept for folk coming from a
table-layout background.
 
R

Richard

Trevor said:
I read an array of comments signaling the end of TABLES, citing them
as old.
Can someone say what CSS code replaces something like the code below,
which I am using frequently?
Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.
I don't know how CSS can replace this kind of structure, and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

<table> versus <div> depends on your needs.
Tables still have their place in the design world. As do divisions.
With divisions, you are much more flexible with being able to spell it all
out in the style sheet before it gets displayed.
Any element of a <div> can be easily changed to suit your needs, as to where
with a table, one cell change within a column or row, could effect all other
cells in that column or row.
Such as the height and width properties.
Can you put two seperate tables side by side? No. But you can put two
divisions side by side.
The choice is yours really.

My remark about "tables are dead" was more of a joke than anything.
 
B

brucie

I read an array of comments signaling the end of TABLES, citing them
as old.

yep they've been replaced by <bureau> which unfortunately are patented
by ikea but the good news is the licence and allen key to assemble
them are free.

slow day
 
T

Talc Ta Matt

I read an array of comments signaling the end of TABLES, citing them

Tables became multi-purpose. Text in rows and columns first and then later
total site layout. Something they were not originally intended for, but does
work.

Like I say, I look at them as being multi-purpose. A few people don't. They
believe that since they were not developed for layout, then they shouldn't be
used for layout.

No major sites have switched from tables to DIV's other than Wired.com, and I
don't think we'll be seeing Yahoo, CNN, Amazon, etc... making the switch for a
long time.
 
T

Trevor

Matthias Gutfeldt said:
Trevor, we had this exact same topic just ten days ago, starting on
September 14, ending on September 17.

<http://groups.google.com/[email protected]>.

You even participated in the thread.

Are you suffering from amnesia, or is there something you really don't
understand about the difference between tables-based and css-based
layout?
- not amnesia.

The arguments presented then and now are very weak, so weak they would
not even stand up to a basic academic analysis. Anything like this
presented academically would be failed almost instantly.

People just blandly state views with almost no basis or reason at all,
like saying - I like apples but not oranges.

Basics of an argument:

- Premise - your underlying statement
- Reasoning based on premise
- Examples supporting reasoning
- Advantages and Disadvantages, eg development costs, future
maintaince costs,
scope, learning curves, life expectancy, universal acceptance, etc...
- Conclusion

This is very different to just saying:

"Trust me, tables are dead"

"Tables should be only for tabular data"

etc

Such arguments are very weak and have almost convincing power at all.
They are forgotten or ignored in a New York Minute, for one simple
reason - they have no substance to them.

Is that clearer?
 
M

Mark Parnell

Trevor said:
<http://groups.google.com/groups?selm=3hn9mvgpl3dlovq8vu72o46iu8tetl2u3l@4
ax.com>.
- not amnesia.

The arguments presented then and now are very weak, so weak they would
not even stand up to a basic academic analysis. Anything like this
presented academically would be failed almost instantly.

Your original comment (quoted above) said that you heard about "the end of
tables". As was cleary explained in the topic Matthias mentioned, they will
always be a part of the specs. Whether they should be used for layout or
not (which seems to be the issue you are questioning) is a different matter.
People just blandly state views with almost no basis or reason at all,
like saying - I like apples but not oranges.

But I like both :-(
Basics of an argument:

- Premise - your underlying statement
- Reasoning based on premise
- Examples supporting reasoning
- Advantages and Disadvantages, eg development costs, future
maintaince costs,
scope, learning curves, life expectancy, universal acceptance, etc...
- Conclusion

Matthias himself gave quite a good answer in the above topic, outlining many
of the issues involved, and addressing each of those "basics":
http://groups.google.com/groups?q=g...e=UTF-8&[email protected]&rnum=13

Those few reasons in themselves should be enough. No doubt you could find
more by googling this and similar groups.

I personally don't think that the disadvantages he mentioned are quite as
bad as he indicates - it is easy enough to hide the CSS from "legacy"
browsers so they still get the content, just not the styles. Modern
browsers generally support CSS reasonably well, especially for relatively
simple layouts. Very little hackery is required for most designs.

IMHO at least part of the reason that the big sites are still using tables
is because it would be a mammoth task to completely redesign sites that
size. They will do it eventually, though.
 
L

Leif K-Brooks

Tables became multi-purpose. Text in rows and columns first and then later
total site layout. Something they were not originally intended for, but does
work.

Unless your audiends is blind, or on something besides a computer.
Like I say, I look at them as being multi-purpose. A few people don't. They
believe that since they were not developed for layout, then they shouldn't be
used for layout.

Because they don't work as well as a layout tool should.
No major sites have switched from tables to DIV's other than Wired.com, and I
don't think we'll be seeing Yahoo, CNN, Amazon, etc... making the switch for a
long time.

So the big guys aren't doing it right. Why follor the leader when he
doesn't know what he's doing?
 
E

EightNineThree

Trevor said:
Matthias Gutfeldt <[email protected]> wrote in message <http://groups.google.com/groups?selm=3hn9mvgpl3dlovq8vu72o46iu8tetl2u3l@4
ax.com>.
- not amnesia.

The arguments presented then and now are very weak, so weak they would
not even stand up to a basic academic analysis. Anything like this
presented academically would be failed almost instantly.

This coming from someone whose (hideous) website is called "logicians.com"

Let's start you off on a basic syllogism:

Idiots use tables for layout.
You've used tables to layout your site.
Therefore, you are an idiot.
 
K

Kris

No major sites have switched from tables to DIV's other than Wired.com, and I
don't think we'll be seeing Yahoo, CNN, Amazon, etc... making the switch for a
long time.

You confuse Yahoo, CNN and Amazon for Jesus.
 
N

Nicolai P. Zwar

Trevor said:
The arguments presented then and now are very weak, so weak they would
not even stand up to a basic academic analysis. Anything like this
presented academically would be failed almost instantly.

People just blandly state views with almost no basis or reason at all,
like saying - I like apples but not oranges.

Basics of an argument:

- Premise - your underlying statement
- Reasoning based on premise
- Examples supporting reasoning
- Advantages and Disadvantages, eg development costs, future
maintaince costs,
scope, learning curves, life expectancy, universal acceptance, etc...
- Conclusion

This is very different to just saying:

"Trust me, tables are dead"

"Tables should be only for tabular data"

etc

Such arguments are very weak and have almost convincing power at all.
They are forgotten or ignored in a New York Minute, for one simple
reason - they have no substance to them.

Is that clearer?


It becomes clear, Trevor, that you are way out of line. First of all,
this is Usenet, not a University. People don't owe you anything, most
certainly not academic analysis at your convenience. You have asked a
question, you have gotten direct and fitting replies to your question. I
don't know about the arguments _then_, but I have read the thread _now_,
and it should be pointed out that _nothing_ in your initial post
indicated that you were looking for any type of discussion, academic or
otherwise. If you are looking for academic discussion, pal, then go
ahead, initiate it. But judged from the way you are acting now, you
don't seem to have the dimmest idea what "academic" discussions are about.

In fact, lets take your original posting apart:
I read an array of comments signaling the end of TABLES, citing them
as old.

You have some nerve asking for academic analysis, when all you present
to begin with are some unsubstantiated claims. You claim to have read an
"array of comments" (where, when, written by whom?) signaling the end of
tables (how so?), citing them as "old" (what's meant by "old"? "Old" in
what way? "Old" in comparison to what?). There is practically nothing
there that could be used as a basis for a series discussion, now, is there?
Can someone say what CSS code replaces something like the code below,
which I am using frequently?

That question has been answered. Especially since you just added a code
snippet to your posting without any indication of what you intend to use
it for.
Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

I don't know how CSS can replace this kind of structure,

But some other people here do, and they have been very helpful in their
answers. Note again that you are _not_ soliciting any type of discussion
in your posting -- something that would be perfectly legitimate -- but
you are merely asking questions and admit that you don't know something.
You have gotten answers. If you want discuss the issue, start discussing
the issue. But don't expect other people to magically read your mind so
they can write their postings to entertain you with discussions. That's
un-academic.
and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

People have told you. Several times. If you still haven't understood,
how do you intend to follow an actual academic discussion? They are
talking about the fact that tables are to be used for structuring data
and that for layouting purposes, CSS is to be preferred.

Now, _why_ CSS should be the preferred over tables for layout is
certainly something that be discussed -- in fact, it has been discussed
many times in various groups already, and undoubtedly it will be
discussed again -- but it's a totally different question from your
original one, and once again: nothing in your posting even remotely
hinted at the fact that you were looking for analysis of such things as
"advantages and disadvantages" or "future maintaince[sic!] costs".

These would be subjects for legitimate questions, no doubt about it, but
how dare you call for "academic discussion" and make wide sweeping
statements as "the arguments resented then and now are very weak, so
weak they would not even stand up to a basic academic analysis", when
you are obviously lacking the most basic essentials for such a
discussion, such as asking the right questions and distinguishing an
"argument" from a "reply" from a "fact" and from an "opinion".
 
N

Nicolai P. Zwar

Trevor said:
The arguments presented then and now are very weak, so weak they would
not even stand up to a basic academic analysis. Anything like this
presented academically would be failed almost instantly.

People just blandly state views with almost no basis or reason at all,
like saying - I like apples but not oranges.

Basics of an argument:

- Premise - your underlying statement
- Reasoning based on premise
- Examples supporting reasoning
- Advantages and Disadvantages, eg development costs, future
maintaince costs,
scope, learning curves, life expectancy, universal acceptance, etc...
- Conclusion

This is very different to just saying:

"Trust me, tables are dead"

"Tables should be only for tabular data"

etc

Such arguments are very weak and have almost convincing power at all.
They are forgotten or ignored in a New York Minute, for one simple
reason - they have no substance to them.

Is that clearer?


It becomes clear, Trevor, that you are way out of line. First of all,
this is Usenet, not a University. People don't owe you anything, most
certainly not academic analysis at your convenience. You have asked a
question, you have gotten direct and fitting replies to your question. I
don't know about the arguments _then_, but I have read the thread _now_,
and it should be pointed out that _nothing_ in your initial post
indicated that you were looking for any type of discussion, academic or
otherwise. If you are looking for academic discussion, pal, then go
ahead, initiate it. But judged from the way you are acting now, you
don't seem to have the dimmest idea of what "academic" discussions are
about.

In fact, lets take your original posting apart:
I read an array of comments signaling the end of TABLES, citing them
as old.

You have some nerve asking for academic analysis, when all you present
to begin with are some unsubstantiated claims. You claim to have read an
"array of comments" (where, when, written by whom?) signaling the end of
tables (how so?), citing them as "old" (what's meant by "old"? "Old" in
what way? "Old" in comparison to what?). There is practically nothing
there that could be used as a foundation for discussion, now, is there?
Can someone say what CSS code replaces something like the code below,
which I am using frequently?

That question has been answered. Especially since you just added a code
snippet to your posting without any indication of what you intend to use
it for.
Each include has a TABLE which is self contained. This means that
basically a series of modules can be written which are encapsulated
and independent.

I don't know how CSS can replace this kind of structure,

But some other people here do, and they have been very helpful in their
answers. Note again that you are _not_ soliciting any type of discussion
in your posting -- something that would be perfectly legitimate -- but
that you are merely asking questions and admit that you don't know
something. You have gotten answers. If you want to discuss the issue,
start discussing the issue. But don't expect other people to magically
read your mind so they can write their postings to entertain you with
discussions. That's un-academic.
and I would
like to know exactly what people are talking about when they say
TABLES are old hat.

People have told you. Several times. If you still haven't understood,
how do you intend to follow an actual "academic" discussion? They are
talking about the fact that tables are to be used for structuring data
and that for layouting purposes, CSS is to be preferred.

Now, _why_ CSS should be the preferred over tables for layout is
certainly something that's open to discussion -- in fact, it has been
discussed many times in various groups already, and undoubtedly it will
be discussed again -- but it's a totally different question from your
original one, and once again: nothing in your posting even remotely
hinted at the fact that you were looking for analysis of such things as
"advantages and disadvantages" or "future maintaince[sic!] costs".

These would be subjects for legitimate questions, no doubt about it, but
how dare you call for "academic discussion" and make wide sweeping
statements as "the arguments resented then and now are very weak, so
weak they would not even stand up to a basic academic analysis", when
you are obviously lacking the most basic essentials for such a
discussion, such as asking the right questions and distinguishing an
"argument" from a "reply" from a "fact" and from an "opinion".
 
T

Talc Ta Matt

Unless your audiends is blind, or on something besides a computer.

From what I undersand, tables do in fact work on blind reader programs in that
the tables are just stripped out and everything is then stacked and read from
top to bottom. Same thing as what would happen with DIV's.
Because they don't work as well as a layout tool should.

That's right, it's a tool. Designers should never feel forced to use any
specific tools.
So the big guys aren't doing it right. Why follor the leader when he
doesn't know what he's doing?

If you really believe that then why don't you contact them, and inquire about a
lead web developer position since their current team is supposedly clueless.

As for not knowing what they are doing.... I'll take it your sites bring in
more revenue per visitor than theirs do. Correct?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
474,079
Messages
2,570,574
Members
47,207
Latest member
HelenaCani

Latest Threads

Top