Collin Davis wrote:
Tables wouldn’t do this. Also, lists are just easier for me to use than tables, and tables create more code weight than do lists. Anybody have thoughts on this?
Well, for me, the deciding factor on using a table is if the elements contained in the table are 2 dimensional. In other words, can they be grouped in two dimensions. For example, a list of population grouped by cities AND age ranges would be two dimensional and would satisfy the requirement for a table. However, you could define a list of population counts grouped by city as two dimensional since one column would have the city name and the other have the population count. Thus, if there is no way to group the elements by row AND column, then it is not tabular data and is just a list. For example, I might provide a table of photos if it were grouped such as follows:
Photo Album
Year | Vacation | Xmas | School
2004 | pic | pic | pic 2003 | pic | pic | pic 2002 | pic | pic | pic
I know this is a crude example and could be handled differently, but since this can be grouped in two dimensions, a table is the best choice. Else, I personally stick with a List. _____
Charles Martin http://www.webcudgel.com [EMAIL PROTECTED]
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
