The first paragraph of this article provides a brief overview of the topic. It discusses the use of frames and tables in web design, highlighting their potential pitfalls and benefits. The article emphasizes the importance of simplicity, careful planning, and thorough testing in creating effective and visually appealing web designs.
Frames have been used in some of the most visually unappealing websites I've ever encountered. However, it's only fair to mention that I've also seen tables used in equally disastrous ways. Frames necessitate the use of a "Frameset" page, which is crucial. If it's poorly designed, the frames will either fail to function or look atrocious.
The Frameset page is essentially a blueprint for the rest of the site. Each section (or Frame) contains a complete webpage, even if it's just an image. The Frameset page instructs the browser where each of these complete pages should be placed. If a page with a lot of information is squeezed into a narrow frame, it can be frustrating for the visitor.
When designing a framed page, it's important to keep it simple. Overly complex framed pages with numerous frames can be overwhelming. The human eye can only process so many sections, especially on the internet. When setting up a framed page, I ask myself a few questions:
If the answer to the first two questions is yes, then proceed with the setup. However, if there's any doubt, consider using tables.
Tables, on the other hand, have their own peculiarities. The most significant one I've encountered is browser compatibility. Netscape and Internet Explorer interpret tables differently. I've found that blending the tags that both browsers can read is an effective solution to this problem.
Tables are essentially a series of rows and cells that allow for the neat organization of information and images. When designing a page using tables, it's often best to leave the border on. This provides a clear view of the layout and how it truly appears, including where the text is placed in a specific cell of a table. I've visited many sites designed with tables and found the text overlapping itself or images. A good rule of thumb when setting text in a table cell is to provide a cell padding of at least 5 pixels.
Both frames and tables should be thoroughly tested with the two most popular browsers. What might look great with Netscape often looks terrible in Internet Explorer, and vice versa. Netscape seems to be more forgiving, especially with tables. If you can get tables to work and look right in Internet Explorer, Netscape will likely be satisfied.
One more thing to consider regarding tables and cross-browser compatibility is the background colors of cells. Netscape reads background images, while Internet Explorer does not. Therefore, it's crucial to ensure that the table's background color blends well with the page's background. This is not a problem if you're using a plain colored background, but it becomes a significant issue for those of us who prefer a textured background. Always double-check!
As for frames, remember that some older browsers do not recognize them, so all your hard work could be wasted. It's always a good idea to create a version of the site that doesn't use frames for those with older browsers.
Whether you prefer frames or tables, or are undecided on which method to use for your page layout, keep these points in mind:
