On 28 Sep 98, franko wrote:
> Maybe I'm missing something, but if you're redrawing both main and nav
> frames each time, why have frames at all?
>
Mm. You may have missed my subsequent post to Barry, in which I asked
the same generic question: "Why use frames at all??" <g>
As I noted in that post I don't like frames generally, for all the usual
reasons: they defy the entire "one URL = one page of information" model
of the Web, and in turn screw up bookmarking and Back/Forward
navigation.
As I also noted, frames are most useful when you need to keep fixed
navigation onscreen in one frame with lengthy documents in another, such
as for technical documemtation. And in this context, the approach I
outlined works quite well. Yes, the navigation frame refreshes each time
you move to a "new page" (frameset), but it *does* remain in a constant
position onscreen. And the reload time is almost imperceptible to the
user, if he notices at all. But he can now bookmark pages, reference them
properly in e-mail to others, and use Back/Forward buttons reliably.
Try it sometime. It does work, within the numerous limitations of how
Netscape ill-advisedly implemented <frame> in the first place. As
generation 4.x browsers become more common, I expect that resourceful
use of CSS/DHTML will in time come to replace the kludgy and hapless
<frame> tag.
-----------
Brent Eades, Almonte, Ontario
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Town of Almonte site: http://www.almonte.com/
Business site: http://www.federalweb.com
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
