To frame or not to frame?
One of the most frequently posted message on the Macromedia Dreamweaver's NG is about frames. It is Murray Summers who posts it over and over. Here is what it says:
The reason for using or not using frames should be based on:
- Your site's needs,
- Your willingness to accept the potential problems that frames can create for you as developer and maintainer of the site and for your visitors as casual users of the site.
I am down on frames because I believe that they create many more problems than they solve. Judging from the posts here, and the kinds of problems that are described, the kind of person most likely to elect to use frames is also the kind of person most likely ill-prepared to solve the ensuing problems when they arise. If you feel a) that you understand the problems and b) that you are prepared to handle them when they occur, and c) that you have a need to use frames, then by all means use them.
Useful Links
- frames Solved | How to Design with frames without problems.
- W3C frames in HTML documents | Multi-view presentation of documents.
- HTML tag reference | Netscape discusses the tags for creating frames and framesets.
- SiteExperts.com | Programming the Body and frameset Elements.
- Javascript.Faqts | Answers to basic questions about frames.
- WebReference.com | Framing the Web.
- IRT.org | Interesting articles about frames.
- Hal Pawluk's web site | frameJammer & framestuffer.
- Master frame Reunion | The CGI way.
- PP:K | frame Parsing.
- AppTools.com | frames are Evil.
- Fourlevel.com | Creating and Managing framesets in Dreamweaver.
