Hi Ron! Here's a short response: if you have not yet drank the w3c web-standards kool-aid, now's the time. Just do it. The Web Accessibility Initiative (WAI) http://www.w3.org/WAI/ should explain why you should avoid use tables for layout purposes.
Here's a longer response: I empathize. I too was *very* comfortable using tables for layout. In retrospect, I think this made it harder for me to acclimate to using CSS for positioning. Can you imagine, especially a few years ago, what a *pain* to try and learn CSS for positioning? For me, I never knew what I was doing right or wrong, I was just pushing/pulling to make things work. I'm a right-brained person who just wants to make it work, and doesn't fancy keeping a detailed list of what browser support what. On top of that, you're training your brain to stop thinking in a grid and think in the CSS box + visual formatting model. It's very different. So yeah, it *is* a difficult transition. No question. I'm still in the process of it myself. But like everything else, it gets easier the more you do it. There are tricks and techniques to make it all work. There are also a lot of good precoded-layout simple layouts out there that can help with an initial build. Finally, it helps to remember that markup is a way to describe the meaning of a document. Thanks to CSS, tables are once again a way to mark up tabular data. Erika PS: the CSS overlords are teeny-tiny people living in your browser who's job is make your page render. ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
