Re: Table formation...

Jay Blanchard wrote:

[snip] Pardon my asking on the eve of your launch, but is a table the most sensible markup for this data? It looks to me like a one-dimensional list that just happens to be presented two to a row. If so, I'd use an unordered list, float each item left, and limit the list width to two item widths. [/snip] Thanks, but I just used what I showed as an example. It is a table products including pictures, features, etc.

time limits always dictate the 'get it working' solution, that said Paul's suggestion is rather better than using a table for a couple of reasons (imho): 1. it saves you having to pre-order/split/etc the original data so that you can then loop them/it in order to dump out a table. 2. it means that when the customer changes the layout your not stuck with re-hacking output code - you just change the display style. non-rigid markup :-) 3. the output you describe sounds like a list of info rather than a table - which for [us] semantics freaks (hi guys ;-) mean an OL or a UL is so much more satifying.