I
Isofarro
Paul Weikel wrote:
[Frames]
If the menu itself is graphically intensive, then there's no problem not
using frames since images tend to be cached by the browser, so only the
actual HTML of the menu gets redelivered on each page. Since most of the
presentational aspects of the menu can be encapsulated in CSS (which is
also cached), the required HTML should be pretty small not to add much
weight to the rest of the page. So the effects you fear are minimal.
[Frames]
Okay, maybe they do seem less professional, but its pretty obvious that my
site is graphically intensive and I dont want to have to have my user
re-downoad the menu each time he/she goes to another page.
If the menu itself is graphically intensive, then there's no problem not
using frames since images tend to be cached by the browser, so only the
actual HTML of the menu gets redelivered on each page. Since most of the
presentational aspects of the menu can be encapsulated in CSS (which is
also cached), the required HTML should be pretty small not to add much
weight to the rest of the page. So the effects you fear are minimal.