Due to the way frames are defined, to include a window to create frames in HTML³ is technically beyond my programming ability(¹); although I took on the task of writing the main program partly to help me improve my programming skills, what is needed here is so completely different that it's a big step forward. It may be possible, however, to bolt in a third party program to do the job.
<P>
(¹)<I><SMALL> at least, it was at the time of writing. I might be able to do it now, but it's a big undertaking and getting the rest finished takes priority.</SMALL></I>
<P>
The arguments for and against frames have waged for some time - some people think they're the spawn of the devil, others that they're the best thing since sliced bread - and in the end it's a personal preference as to whether you use frames on your site; personally I don't like them much, but do use them when the situation arises.
<P>
Frames can be useful for setting up a simple way of navigating the site which only has to be done once, and then you can get on with the business of producing information without having to worry about fancy trimmings all the time. As such I generally tend to use frames when designing a site for a client who will probably want to keep adding to the site, but doesn't necessarily know much about HTML - I've already set up the pretty stuff and the navigation in the outer frames, so they only have to produce plain text files if the worst comes to the worst. It should also be remembered that it takes less download time if you use frames to define one navigation bar, rather than duplicate the same 5K or so at the top of every page.
<P>
However, most designers now seem to be shying away from frames in favour of using tables to break a page into clearly defined areas; although it means slightly longer download times - not seen as a problem since the advent of faster modems no doubt - it does mean that the reader can jump in at any point (for instance, if they've come via a search engine it's very unlikely that they'll go to the initial frame-defining page first) and they'll still get the full experience of the site. It also means that to show a page of information you only need to keep one page up to date, instead of three or four to define and fill the frameset. As a final warning against frames, it should be noted that Acorn browsers can't handle a history of frame contents, only of URLs visited, so the back and forward buttons on your browser won't work using frames, but you don't have that problem using tables. Using tables can mean repetition, so I advise using SSI to include a standard header and footer on pages - it also makes a site redesign much easier when all you have to change are two files!
