3 ms·
> takes like maybe ten minutes of reading a how to guide as to how to figure out how to do it with real css. Sorry but I'm skeptical. If you could prove this
by evanrmurphy 16y ago
> takes like maybe ten minutes of reading a how to guide as to how to figure out how to do it with real css.
Sorry but I'm skeptical.
If you could prove this by sharing a paragraph or two (should be all it takes, right?) teaching how to use CSS to build reliable layouts I would be grateful.
- akkartik 16y agoMe too. I suspect what he meant was that you can come up with a simple layout with 10 minutes of reading, but that's a strawman. The real problem is that it's extremely easy to rapidly make a once-simple layout a nightmare to maintain or debug. With bitter experience I've realized I need to be extremely disciplined when I use the CSS directives margin, padding, and float. Everything else is relatively straightforward, with localized implications. But anytime you mess with the box model itself you really need to think about the big picture of your page's layout.
- jws 16y agoStep one is to abandon your initial requirements and rewrite ones that are compatible with robustly portable CSS. After that I think the quoted statement works.
- evanrmurphy 16y agoCan you gives some examples of requirements that must be abandoned?
- flyosity 16y agoThere are many CSS books that give concrete examples of various layout types that work in all browsers. Dan Cederholm wrote one of the best: http://simplebits.com/publications/bulletproof/ http://simplebits.com/publications/bulletproof/
- evanrmurphy 16y agoThank you, this look like a good resource. :) However, a book is a very different investment from "maybe ten minutes of reading a how to guide".
- flyosity 16y agoIf you want that, see this: http://www.maxdesign.com.au/articles/css-layouts/ http://www.maxdesign.com.au/articles/css-layouts/ It was written in 2002. Cross-browser layouts are a "solved problem" :)