|
|
Posted by Mimic on 07/19/05 02:23
Onideus Mad Hatter wrote:
> On Fri, 15 Jul 2005 12:53:48 GMT, Michael Winter
> <m.winter@blueyonder.co.uk> wrote:
>
>
>>On 14/07/2005 23:41, ^reaper^ wrote:
>>
>>[snip]
>>
>>
>>>Thanks for the input, Michael.
>>
>>You're welcome, though Mike will do. :)
>>
>>
>>>Wrt to the other (globals, arrays, and bears, oh my!), making the changes you
>>>suggested makes little sense in context of requiring more complex
>>>serverside processing.
>>
>>Moving to an Object instance is about as complicated as changing:
>>
>> ... = new Array(); or = [];
>>
>>to:
>>
>> ... = new Object(); or = {};
>>
>>I'd double check, but I can't seem to access anything at the moment, so
>>I'd take that with a pince of salt for now if I were you.
>>
>>Creating a proper Map object would be more involved, yes, but a more
>>robust solution.
>>
>>
>>>Furhtermore, I'm not seeing where replacing the canvas overlay divs
>>>with a table buys me anything.
>>
>>I like structure. Don't know about you. Using a table would also allow
>>you to remove the id attributes as you could use the cells and rows
>>collections to access the elements like an array. If the 'addresses' are
>>computed server-side, rather than a long list of literal y0x0, y0x1,
>>etc., this approach would be similar and the calculation could be
>>performed on the client.
>>
>>
>>>Whereas for teh table, I would need to set row height and column
>>>width for each cell (which is, of course also easily computed)
>>
>>Despite the comment in brackets, you seem to be painting that as more
>>complicated than it is. As I recall, the symbol table is evenly spaced,
>>so the columns would be of equal width, and you know exactly how high
>>each row needs to be. As I see it, you don't need to do any calculations
>>at all.
>>
>>
>>>In fact, I did just such a thing for the menu (e.g., using a table for teh overlay). As you can see, when viewing teh
>>>page in firefox, the table ends up scrunched to the left (even with
>>>explicitly stated table & column widths).
>>
>>The problem, as I said in my previous post, is that the positioned
>>container DIV element doesn't have an explicit width. Without being able
>>to see the markup again I can't say exactly why that's so.
>
>
> ...um, that's why God invented style sheets. DIV in and of itself
> doesn't really do anything without style sheets. Really, there is no
> sane reason why ANYONE should be using tables anymore, that's just
> archaic, sloppy, imprecise web design at its best.
>
> --
>
> Onideus Mad Hatter
> mhm ¹ x ¹
> http://www.backwater-productions.net
Nice to hear that from you. However, tables should be used, just used
correctly...
CSS is for layout
Tables are for displaying tabular data.
Simple as :D
--
Mimic
"I can speak to anyone in the world, I can get any information I want, I
can goto new zealand in 0.384 seconds, why would I want to go outside?"
ZGF0YWZsZXhAY2FubmFiaXNtYWlsLmNvbQ== ( www.hidemyemail.net )
"Without knowledge you have fear. With fear you create your own nightmares."
"He who controls Google, controls the world".
Navigation:
[Reply to this message]
|