#1
  1. <blah>
    Devshed Newbie (0 - 499 posts)

    Join Date
    Dec 2002
    Location
    Melbourne, Australia
    Posts
    483
    Rep Power
    33

    Post Using CSS instead of nesting tables!??


    I realise table nesting makes a page load slower, and the less nesting the better. -But I havent found any good reason (due to CSS incomptability or browsers not implementing the DOM etc properly) to supplement my table nesting with CSS/div/layers

    Can someone show me a complex site which implments CSS and 'less' table nesting? Even point me in the right direction of a good CSS resource online..

    Thanks in advance.
  2. #2
  3. Senior Polecat
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jun 2003
    Location
    Jersey (the original version)
    Posts
    210
    Rep Power
    11
    I've only developed one site which used css-p instead of tables and spent absolutely ages trying to get it to work in all browsers (in the end I had to give up on NN4).

    I can't show you the site as it isn't public yet.

    the best CSS site i've seen is http://www.alistapart.com/ but it isn't very complex. I think that, until the browsers catch up and provide 100% compatibility accross the board, talbes are going to remain the prominent designers tool.
    Quidquid latine dictum sit, altum viditur.

    http://www.XSet.co.uk
  4. #3
  5. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jun 2003
    Posts
    17
    Rep Power
    0
    There is a tutorial at http://developer.apple.com/internet/...csslayout.html that covers converting a fairly complex nested table layout to css.
  6. #4
  7. <blah>
    Devshed Newbie (0 - 499 posts)

    Join Date
    Dec 2002
    Location
    Melbourne, Australia
    Posts
    483
    Rep Power
    33
    Thanks dudes, but nothing still convinces me to use CSS instead of nested tables, even if it will make my pages load faster, taking into these points alone
    As quoted from http://developer.apple.com/internet/...csslayout.html
    Layout limitations: The fact is that CSS layout will not currently allow you to do everything you can do with tables. This can be a real frustration, and has stopped many people from exploring what CSS can do. (I'll show you in this article that CSS
    can do quite a bit.)

    Slight differences in browser display: CSS is difficult for browser makers to implement, and the W3C recommendations can be vague and confusing. So you can expect even the most recent browsers to behave differently when dealing with some aspects of CSS layout. Keep your layout simple enough and you will likely get a nearly identical display in Opera 5+, NS6, and IE5+. But as your layout increases in complexity, the odds that different browsers will render pages differently also increases.

    Difficulty in switching from tables to CSS: For designers and developers accustomed to wrangling tables, using CSS for layout can be a confusing change. There is a "table mentality" that we developers have taken on over the years, and we are in large part unaware that it exists. Some take offense when this is pointed out, complaining instead that CSS is just difficult and non-intuitive. But if you were accustomed to driving a car with a steering wheel and you were then asked to head out on the freeway in a car steered with foot pedals, you certainly wouldn't be offended at the suggestion you had a "steering wheel mentality." The fact is, we are generally comfortable with tables. CSS layout is different, but we must not confuse differences with increased complexity.
  8. #5
  9. No Profile Picture
    :: cerebralshock ::
    Devshed Newbie (0 - 499 posts)

    Join Date
    Aug 2002
    Location
    Everywhere & nowhere.
    Posts
    133
    Rep Power
    12
    See http://forums.devshed.com/t64196/s.html for a similar debate...

IMN logo majestic logo threadwatch logo seochat tools logo