Heheh..ta for that Qui. The easiest way to learn to do frames is to go here (http://junior.apk.net/~jbarta/version.html) , and grab the tutorials. There's one on frames, one on tables and one on basics, and lots of other stuff too.
Basically, (as it was explained to me) the FRAMESET declarations replace the usual BODY declaration - and although everyone keeps saying that they should be in the HEAD container tags, the tutorials I've read say they're not. Um. Definitive answer to that one someone?
The numbers that Qui's put in tell it how many pixels to use for the frame, and the * tells it to make the next frame elastic.
Erm. This is Qui's code in the format you'd usually write it (and with the missing /Frameset closing tag put in http://www.wireplay.co.uk/ubb/tongue.gif)
<BLOCKQUOTE><font size="1" face="Arial, Helvetica">code:</font><HR><pre>
<html>
<HEAD>
<TITLE>The Main Frame Page</TITLE>
</HEAD>
<FRAMESET rows= 130,* FRAMEBORDER="0" FRAMESPACING="0" BORDER="0">
<FRAME SRC="oppslist.htm" NAME="oppslist" SCROLLING=no frameborder=0>
<FRAMESET cols= 130,* FRAMEBORDER="0" FRAMESPACING="0" BORDER="0">
<FRAME SRC="oppexp.htm" NAME="oppexplan" FRAMEBORDER=0 SCROLLING=auto>
<FRAME SRC="plain.htm" NAME="oppdetail" FRAMEBORDER=0 SCROLLING=auto>
</FRAMESET>
</FRAMESET>
</html>
[/code]
What this tells the browser is to first of all split the window into 2 frames (that's the <FRAMESET ROWS=130,* etc.> bit. (I'd usually put the COLS one first, but each to their own...). The frames are divided according to the numbers - the first frame is 130 pixels tall (from the top of the window) and the second frame is what's left over (it's important to use those *'s - you'll make a right pig's ear of a page if you don't).
Now we tell the browser what to put in the first frame (that's the one that's 130 pixels tall):
<FRAME SRC="opplist.html" NAME="oppslist" etc>, and call it "oppslist" (the name is so that we can change the URL in that frame witout affecting the others, or at least that seems to be it's most practical use...you can use it in Jscript too. Now that we've done that, we're onto the next bit. But instead of putting a source file in, we want to split this frame again, so we put another <FRAMESET> tag in, like so:
<FRAMESET COLS=130, * etc.> (the other attributes do stuff, but it's more important to understand the basics before fiddling with attributes)
So now we're saying "Take the frame that we defined as elastic before (*) and divide it again - into 2 frames, one of which is 130 pixels WIDE (we've used COLS= rather than ROWS= this time), and the other fills what's left. What this would give us in practical terms is a page that looks a bit like this:
<BLOCKQUOTE><font size="1" face="Arial, Helvetica">code:</font><HR><pre>
___________________
|oppslist |
-------------------
| o|oppsdetail |
| p| |
| p| |
| e| |
| x| |
| p| |
-------------------
[/code]
I've put the names in to try to make it clearer what we're doing to it.
so what we've done is divided the screen up, and then told the browser what to stick in them. The FRAMESET tags equate to individual BODY tags for each frame, and the FRAME SRC tags tell the browser what you want in the frames.
Simple? Erm. Yes, well. Just read the tutorial and all will become clear http://www.wireplay.co.uk/ubb/smile.gif.
Ele
[This message has been edited by Elethiomel (edited 19-09-1999).]