My opinnion is this: both div and table are html elements. Css is styling language for both div and table (and all other) html elements. You can also make the site structure with <ul><li> elements. I understand it is new religion among web developers to glorify div element above table, but that actually has nothing to do with css.
I prefer using divs instead of tables as well when it is possible. As I said in previous post (which is btw not yet published while i write this one) it is not a big problem to create a custom skin with div elements when the site structure and modules selection are known and final. The problem is to make a general purpose skin with divs, and that is because of variety of modules that could be later implemented in it. Our expirience has shown that tables are still better solution for that. We are hosting over 100 portals with more than 60 modules from various vendors installed on our DNN host server.
I would be really happy to see the example of pure div based DNN skin that works well in all browsers with many different modules, without JavaScript and hacks. If any of you could send me a link to it i would be grateful.
Quote: "well thats what a css file is for :)" - my point exactly.
If I took the name ZenDIV for my skin this conversation would make more sence, but as much as I know about zen and about css I still stand behind ZenCSS name for my skin.
Thank you for your feedback.