While I agree that traditional frames have their limits, they also have
their uses.  The key is to carefully consider their use.  On one hand they
allow you to quickly and easily create navigation structures that make sense
without spending time/sweat to develop a similar system without frames.  On
the otherhand, they can be somewhat troublesome to use properly.   Bottom
line is that each developer has to make their own judgement on when/where to
use frames.

One thing I hate about frames, but understand it and can work around it, is
the refresh problem.  If I'm developing a page, and that page is contained
within a frame, I have to remember to right click the frame, then do a
refresh from the context menu.  Doing an F5 or CTRL-R refreshes the entire
frame, which forces me to navigate back to the page in question.

>>- You cannot bookmark an individual page
>>Good! People should always enter the site through the login page.

The security system I typically use prevents users from viewing unauthorized
pages without loging in - but it doesn't force them to always start at the
login page and then navigate to the page in question.  They can bookmark
particular pages (when I'm not using frames), and the page will still be
secure. (I think this is pretty basic, but if anyone wants to know how,
contact me off list).

If I don't need to worry about Netscape, then IFrames are VERY useful to
provide updates and such without having to reload an entire page.

My thoughts.

Shawn Grover

-----Original Message-----
From: Gyrus [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 05, 2002 10:25 AM
To: CF-Talk
Subject: Re: Impending session timeout warning methods?


Here's A List Apart's list of problems with frames, with my comments on
how this works for private, password-protected web apps:
(http://alistapart.com/stories/frames/)

- You cannot bookmark an individual page
Good! People should always enter the site through the login page.

- You cannot email a reference to a page
Good!

- You cannot link to a page
Good!

- Browsers can have problems with Back/Forward
I think this is just older browsers. Well, I only do CMS's for 5+
browsers...

- Framed sites are more difficult for text-based and speech browsers
As above, I limit entry to special CMS's anyway.

- Inexperienced designers can make all sorts of mistakes with frames
I *think* I'm OK on this one :-)

Plus, of course, search engines will have a hard time indexing the site.
Good! I have the ROBOTS NOINDEX meta tag in all the pages anyway.

Maybe I'm bashing this point home a bit too much, but I'm (1) curious to
see if there's any holes in my theory, and (2) quite amazed that I've
discovered after all these years a good use for frames!

- Gyrus

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- [EMAIL PROTECTED]
work: http://www.tengai.co.uk
play: http://www.norlonto.net
- PGP key available
~~~~~~~~~~~~~~~~~~~~~~~~~~~~


______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to