Reply to Re: Table problem

Your name:

Reply:


Posted by Barbara de Zoete on 01/03/06 21:50

On Tue, 03 Jan 2006 20:28:46 +0100, Lüpher Cypher
<lupher.cypher@verizon.net> wrote:

> Barbara de Zoete wrote:
>> On Tue, 03 Jan 2006 20:06:07 +0100, Lüpher Cypher
>> <lupher.cypher@verizon.net> wrote:
>>
>>> Barbara de Zoete wrote:
>>>
>>>> No, they are essentially different. Really. In the second table the
>>>> data in the spans are logically still in one data cell. In the first
>>>> example the data is split up, logically, and put into two seperate
>>>> data cells.
>>>
>>> Well, would it really make difference? You simply use the first table
>>> for logic separation of data
>>
>> I thought one was _not_ supposed to separate the data. The data is in
>> one data cell and I presume it is there, in one cell, for a reason, and
>> thus is supposed to logically stay in one data cell. That is why I
>> think you shouldn't be making two data cells of it (still, if subsiding
>> to table layout, all of this goes out of the window of course).
>
> Well, then, I can argue that, since you need part of that data on the
> left and the other part on the right, the original data consists of two
> "sub-datas" :)

Nice argument.

> And hence splitting into two cells :)

In some odd way you just proved my instincts to be correct on how tables
and layout have nothing to do with each other[1]. Well, sort of. At least
to me you did :-)

Because <more serious now /> you do have a point. If the data in one cell
needs to be seperated so obviously as is proposed in this case, one is
probably dealing with two different sets of data anyway. Than the table
needs an extra column with a column 'lable' and all. Presuming we're not
talking about:

.--------------------.-----------------.
| item | Price |
|====================|=================|
| Book | € 23,00 ea. |
|--------------------|-----------------|
| Good Book | € 42,00 ea. |
|--------------------|-----------------|
| Free advise | Yeah, right :-) |
`--------------------'-----------------'

Where the €€ have to stay on the left and the numbers (and the 'ea.') have
to go to the right. Although, rethinking that, you could argue that the
sign for euro indicates a valuta and therefore could go in its own column
labled 'valuta', and the ea. indicates the amount the price is valid for
and could get a column of its own labled 'per'.
Hmmm, that sounds about right to me. I just seem to have proven your
argument, I think. :-)





[1]unless the layout of the table is there to support visually the logic
that is there between the column- and row lables and de data in the data
cells

--
,-- --<--@ -- PretLetters: 'woest wyf', met vele interesses: ----------.
| weblog | http://home.wanadoo.nl/b.de.zoete/_private/weblog.html |
| webontwerp | http://home.wanadoo.nl/b.de.zoete/html/webontwerp.html |
|zweefvliegen | http://home.wanadoo.nl/b.de.zoete/html/vliegen.html |
`-------------------------------------------------- --<--@ ------------'

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация