Ok, now I agree and disagree with many of the comments here, but to touch on a few I'd like to make some brief points.
Just to state, I've been utilizing and creating with HTML for 8 years, so I have a little background.
First of all, it's true that tables play a major role in the creation of a well-built and functional website. They are the skeleton to the entire page and if used correctly will allow pristine viewing and editing. Most pages you see on the internet now are very versatile when it comes to cross-browser testing and resolution-fitting because of their ability to use relative percentages in their embedded tables.
Secondly, iFrames are new and being new and having the word "Frame" in their title immediately causes some bad aura around their existance. Frames always receive a heavy blow because of their limitations on search engines, and the annoyance of the size limit. They also lock pages into a set shape so that any pages that need more room will need to be completely different during the creation method. This is one of the reasons that iFrames were created in the first place. Not only are they embeddable anywhere in the document, they can be automatically resized via a little javascripting, and they can be hidden from view or popped out on pages that don't need them. Again, when properly utilized they can prove to be a fine tool. I use iFrames in a number of my web layouts and have never found them to be a problem. They allow me to create pages that need only load once, hence speeding up the sites performance in imaging no matter what the connection speed, and allowing caching to do it's job. No longer does the screen blink to white between clicks.
Naturally I think that CSS was an excellent invention and saves much room in the long run. Visually it gives a similar effect to the user, but not to the editor, and I find it much easier to draw up my plan in photoshop, slice and tabulate it to see how it looks, and then convert over to CSS. This three-step process takes no time at all, and allows you to nip & tuck anything needed. Compression of HTML through simple means of cleaning up your code and replacing redundant code is a legitimate and required step in the web creation process.
...My two-cents.
09-17-2005, 12:41 PM
Kavacky
Seems that you have learnt nothing during these 8 years.
Tables for page layot? This is enough to ensure that I`m right.
