How to determine whether to use framework technology in web design

 

The most common use of a framework is navigation. A set of frameworks usually include a frame containing a navigation bar and a frame for displaying the main content page.

However, the design of a framework may be complicated. In many cases, you can create a web page without a framework, which can achieve many of the same effects of using a set of frameworks. For example, if you want to display the navigation bar on the left side of the page, you can use a set of frameworks to represent your page, or you can only include the navigation bar on each page of the site.

 

Many professional web designers do not like frameworks, and many web users do not like frameworks. In most cases, this dislike is caused by websites that use the framework poorly or do not need to use the framework (for example, reload the frame set of the navigation framework whenever a visitor clicks the navigation button ). If the framework uses the method (for example, to keep the navigation controls in a framework static while allowing changes to the content of other frameworks), these frameworks may be very useful for some sites.

Not all browsers provide good framework support, and the framework may be hard to display for visitors who cannot navigate. Therefore, if you really want to use a framework, you should always provide the noframes section in your framework set to make it easy for visitors to view those frameworks. You 'd better also provide an explicit link to the site's frameless version for visitors who do not like the framework even though their browsers support the framework.

 

 

The Framework has the following advantages:

The visitor's browser does not need to reload navigation-related graphics for each page.

Each frame has its own scroll bar (if the content is too large, it cannot be displayed in the window), so visitors can scroll these frames independently.

For example, if the content page in the frame is long and the navigation bar is in different frames, visitors who scroll down to the bottom of the page do not need to scroll back to the top to use the navigation bar.

The Framework has the following Disadvantages:

It may be difficult to achieve precise image alignment of each element in Different frames.

Testing navigation may take a long time.

The URLs of pages with frameworks are not displayed in the browser, so it may be difficult for visitors to set a specific page as a bookmarkdonor (unless you provide a serverCodeAllows visitors to load the frame version of a specific page.