The BIG problem with the theory of "separating logic/content from presentation" is that you just can't do it! Take the <p> tag, for example. It neatly separates chunks of information in both a structural AND VISUAL WAY. How can we deal with that? Besides, most experts are slowly coming to the conclusion that there's not only no way to separate content from presentation, there's also no need for it. Presentation is part of the content, anyway!

Another point frequently missed by "purists" is that every design has an underlying layout grid, that basically mirrors the behavior/attributes of a table. Unfortunately, most of the initial CSS proponents didn't have a design background, so these issues escaped them (that also explains their ugly websites!). To the point that they ignored the simple fact that CSS is a concept (down to the name of "stylesheets") derived from print design.

I guess until CSS 3 (or future versions) takes care of these issues, we are best adviced to go with hybrid layouts, as you point out. But then again, once that's done, then new issues will crop up: what about text wrapping around pictures (like the "runaround" feature in Quark Xpresss)?...   

>The main problem with the hybrid layout is that it does not allow full
>separation of presentation and logic.  Other than that (which is the primary
>complaint of style sheet proponents) I've no problem with it - that's what
>I'm using, in fact.
>
>
>
>Take a look at some of the links in this thread however - you'll see plenty
>of tirades against tables (some more intelligent that others).  I agree with
>you - there's not much basis there.  However being able to separate content
>from presentation IS a good thing - as long as that presentation is flexible
>enough and style sheets often aren't.
>
>
>
>Tables, according to purists, are defiantly not for layout - they are not
>just containers.  They (again, according to purists) are purely for the
>display of tabular data - they should never be used for layouts.  We use
>them for layouts simple because they're so damnably GOOD for layouts (much
>better than style sheets for many tasks), but they weren't actually designed
>to do that.
>
>
>
>I don't believe that CSS offers everything needed in terms of page layout -
>this is clearly the case since you can't make many simple layouts.  I think
>that positioning of elements is pretty much the definition of layout
>capabilities - I'm not sure what you mean there.
>
>
>
>Jim Davis
>
>
>
>
>
>  _____  
>
>From: Irvin Gomez [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, May 26, 2004 6:26 PM
>To: CF-Community
>Subject: Re: Damn CSS... Damn it to hell!
>
>
>
>If you're very familiar with CSS, then you'll know that CSS doesn't offer
>any layout capabilities, beyond the styling and positioning of page
>elements, like tables and their common counterpart, the <div> tag.
>
>Tables and div's are just containers for other tags. As such, they are the
>building blocks for your web page. CSS helps you use them as needed. What
>you choose as the basis for your layout is up to you.
>
>I know I didn't tell you anything you didn't know. My point is that CSS
>already offers enough for you to create anything you might need in terms of
>laying out the page.
>
>After all, what's wrong with the hybrid layout technique we discussed?
>
>
>
>  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to