Re: Frames and Documents (fwd)

Matthew James Marnell (marnellm@portia.portia.com)
Sun, 15 Sep 1996 11:58:00 -0400


Message-Id: <199609151558.LAA27108@portia.portia.com>
To: www-html@w3.org, www-style@w3.org
Subject: Re: Frames and Documents (fwd) 
In-reply-to: Your message of "Mon, 09 Sep 1996 16:07:52 PDT."
             <199609092308.QAA20845@greece.it.earthlink.net> 
Date: Sun, 15 Sep 1996 11:58:00 -0400
From: Matthew James Marnell <marnellm@portia.portia.com>

Frames, frames, frames......

An idea.  Each document keeps it's own ideas of what frames
it should contain.  Example:

<html>
<head>
<title>Subframe Title</title>
<frameset name="Site Frames" href="/frames/site.frame.html">
<frame name="this" number=3>
</head>
<body>
....
</body>
</html>

This way, documents with the same frames, within a sufficiently
intelligent browser can bookmark on the content, while navigation
information or whatever can be kept externally.  The site frame file
describes which frames appear on the screen and where the current
document, ie number=3, should appear in relation, while the current
document is the one that would be bookmarked.

This could also work well for dynamic documents such as cgi created
documents, which could work something like:

Document = http://www.example.com/cgi-bin/search.cgi?foo+widgets

<html>
<head>
<title>Subframe Title</title>
<frameset name="Site Frames" href="/dynaframes/search.023740.html">
<frame name="current" number=4>
</head>
<body>
....
</body>
</html>

and /dynaframes/search.023740.html could contain whatever frame specific
info is needed to render the current document, or the current document
could have and additional frame spec, such as:

<frame name="dynamic 3rd frame" number=3 href="/dynaframes/3/search.023740.h
tml">

and a more generic frameset document which would stipulate where the
3rd frame should go, and its default document, that would be overridden
by the frame statement (above) to place the dynamic frame in it.

This way the bookmark http://www.example.com/cgi-bin/search.cgi?foo+widgets
would again be created dynamically when selected, but not necessarily
with the same frames, and yet still look similar to what the browser
was expecting.

If this wasn't clear enough, or someone would like a clarification, with
diagrams, and even better examples of the tags and attributes as well
as some more realistic example documents, write to me, and I'll try
to do better after I've thought about it a little more (this idea
just came to me while reading through a weeks worth of back www-html/
www-style list messages).

Matt