|
d a v e -> RE: why tables, not frames? (6/4/2004 7:56:21)
|
quote:
ORIGINAL: briesmith We're just about finishing the development of a large ASP driven website which is totally dependent on frames. At the outset the developers were riven by argument about frames; whether or not to use them. The pro-frames camp won the day and we went ahead with a frames based design. The advantages are clear in terms of performance, screen stability and page management. CSS and/or tables remain available without restriction and menuing is, if anything, facilitated. > what perfromance gain is there in using frames when you have at least 2 times as many html doucments? screen stability is a question of good design and site architecture. css and/or tables are 'available' whether or not you use frames. how do you account for differnces in screen settings (e.g. 800x600 etc) when designing menus where differnces are likely to result in scroll bars appearing? you can't use dropdown menus unless they fit in the frame as they won't display across frames. Relying on ASP and supporting classes means that heavy processing loads are placed on the server and significant quantities of code are sent to the clients. Reducing the amount of screen area that changes with each page access helps to mitigate the impact of these two factors. > your code should be lean in the first place Additionally, limiting the amount of screen area that changes also helps with readability. Frames allow headline graphics and menus to remain on screen without "flickering" or, on slower systems, slowly refreshing each time a page is accessed. > users are *more* used to using unframed pages than framed pages so readability is again down to good usability. headline graphics are cached and will simply be displayed again without the need for downloading. Text and other graphical material in the "content" frame scrolls independently of the other frames. Users as a result see a consistent screen structure and the menus remain available at all times. > this is about the only 'advantage' i see in frames, but users are so used to the non-frame left menu, shortish page structure that it isn't a problem anyway. As an aside, an understanding of "content=" and iframes has turned out to be important; without it, maintaining the consistency of the frames and some aspects of navigation would have been difficult. I would say if a frames approach is right for what your business website is trying to do then use it and pay no attention to purists and theoreticians. The old concerns about crawlers not finding frame contained content don't matter if your website is a commercial application that users will either come to or not and with the increasing reliance on paid-for page ranking the importance of crawlers/spiders is declining. And always remember that if your content is ASP or otherwise script generated, crawlers and spiders won't find it anyway. Not all web activity is "search and surf"; more and more site visits are deliberate and repeated; think of Amazon, eBay, DELL and so on. If you are building a website to cater for the kind of needs Amazon visitors, say, have then forget about frames from a conceptual perspective and ask yourself " would my website offer better performance, improved visitor experience and be easier to develop and maintain if I used frames?" If the answer is "yes" then so be it. how do you get around bookmarking, printing, refreshing/revisiting the page (when it goes back to the original frameset)? users that require screen readers or other devices for navigation can easily find framesets confusing and if you change two frames (say one updates with content, the other to indicate which page in the naviagation you are on) frames are harder to implement for new authors IMO frames are mostly for lazy developers who don't know any better. i can't think of one respected site that uses frames and i am in no way convinced of their advantages (if any) outweighing their considerable disadvantages. another potential problem i just thought of could arise should you wish to port your content to mobile devices (i.e. what do yuo do with the frames??), but i have very little knowldge of that so i don't know.
|
|
|
|