Hi 

I have now gotten the hang of using only divs and no tables in skins (Thank you MS Expression 2).
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/109/threadid/277722/scope/posts/Default.aspx

It really is quite a revelation to see how simple it can be and its fantastic to see the same results in different browsers.

My question is about the tables used in MinimalExtropy and its container family.
Are the tables used simply to provide some legacy module compatibility ?

Now I have skins without tables I want to make containers the same way. I am wondering if there is any downside to this.

Suggestion:
Many people may be struggling with "no tables - css skins". Would it not be a good idea to include examples in future releases for people to work and learn from.
I might also say that the MinimalExtropy skin makes a great fuss with its images. Why have 3 image elements for the top bar - why not just one?

Thanks

Ian

I talk myself a lot in this forum too. haha

I am not quite ready to do "table-less" skin yet since many modules are depending on the table tag. It's probably a dumb question - can you (or someone else) explain why a tableless skin is better than table one?  Yes, I did google "Tableless web design". I still don't see huge benefits, which convince me enough to create a tableless skins.  I myself created the tableless website before. However, it took me a while to adjust browser compatibilities of the page. The final product looked great and easy to change stuff in css. But I don't know if i want to do it again in near future.

Hi Meth,

Yeah, but when i think about the balance between the benefits & effort that i need to put on it,, I am not ready to do the table-less structure jsut yet.