Frames Supremacy

Frames, as a web technique, have well known drawbacks. When you create a site on your own, that can be a problem you may not want to deal with. But with KSW, we fixed ALL frames drawbacks - and since code is generated for your site, you stay clear from any such issues. On the other hand, in some respects frames are unbeatable and unmatched by any other web technique; download speed, screen flicker/reloading, resizing, and other such web traits are dealt with masterfully with frames.

Frames and KSW
Numerous useful sites (Microsoft MSDN included) use frames plentifully. Why? Because frames have features nothing else can replace! But then, what about the drawbacks of frames? With KSW, we've taken care of them ALL. We also used some so called "drawbacks" of frames to your advantage. Here they are, detailed, one by one:

1. Issue: Since each frame contains a separate web page file, you have to create several HTML files to make one complete "web page".
Solution: KSW creates the frameset and the additional HL frame automatically. It's only the topics that you create yourself. So you create one and only one page per browser window.

2. Issue: Frames make a site hard for search engines to search.
Solution: See Google friendly site.

3. Issue: Frames can be simulated with CSS positioning.
Solution: One of the major web technology flaws is that a user must endure constant flickering and page reloading for some if not all basic operations one does on a page. This is, to say at least, unpleasant. When using CSS-simulated frames, this problem exacerbates; plus, there is a tremendous increase in download time for each and every topic request. With KSW, the HI frame does not need reloading at any time. It's only the topics that change, when and if you decide. Normal topic download time is minimized to strictly topic contents.

4. Issue: Adding to Favorites may fail for a page in a frame.
Solution: This is true. But when the frame is removed from the frameset (click 'close' in HI), and fills the entire screen, it can be bookmarked accurately. KSW puts a permanent "How to Add Page to Favorites" link at the very bottom of the HI frame, that gives the user a clue at any time. Returning to the frameset can be done with 'Back' in browser, or by return links that are easy to implement (see Return Links), but not mandatory.

5. Issue: Printing a page in a frame can be confusing.
Solution: Disagree. Just click a frame anywhere and print. The exact page in the clicked frame and not anything else will be printed.

6. Issue: You just entered a frameset. Pressing 'Back' in browser may refuse to perform.
Solution: Only happens with poorly coded framesets. With KSW, 'Back' always works.

7. Counter-issue: CSS-simulated frame problems.
Solution: Don't use CSS-simulated frames! Problems like re-sizing or stick-to-position (otherwise, the HI scrolls along with everything else!) are very difficult to fix, or close to impossible - like in IE6. And all this at your expense, as it clutters every topic's code. KSW keeps topics separate from any HI code. You are the master of your topics - they contain your code only and nothing else.


Conclusion: For a KB web, where information is presented through a large number of topic pages, the frameset is THE solution that's most excellent and unbeatable.