Originally posted by bretticus
In my experience, I've really only seen frames pages for side navigation where a Web designer wants his or her menu to remain stationary with scrollable content in the main frame.
Personally, your code might flow more cohesively if you stick to include files. I think what it really comes down to is what you feel will work better for you. It's your Webpage afterall.
Actually i have no desire to scroll just the main part of the page, scrolling the whole page is fine. My main concern is passing form values. is it easier with frames or tables? I've used tables in the past, and what i do i pass the form values to the main file, and then submit those to the functions that are called from the main site.
Some psuedo code as an example of what I mean when dealing with tables
pass "hello" to index.php
index.php stores "hello" in $var
do a bunch of condition checking in index.php and if all is true then.
pass $var in a function that writes $var to the screen
When dealing with frames, well I never really used frames before, but from my understanding each frame can contain a different page to display. with this setup I imagine that I could pass the form values directly to the proper page, instead of having to pass it to the main file, and then pass it to a function.
