Dotnetnuke skinning whitepaper translation record (term and win Client Program)

Translation:
Terms

 

The term "skinning (skin)" is something that is hard to explain in words. Simply put, a skin system provides you with a static layout, however, it allows you to modify colors and styles and even use your images instead of the original ones. Another skin system allows you to customize the appearance of any content other than the content. There are obvious differences between the two methods. You need to select the solution that best suits your application according to your business needs.

 

Windows client program

 

Skin technology has been popular in Windows client programs for quite some time, this may make you think that the same skin system can be applied to your web application without too much effort. However, this idea has proved to be a mistake.

 

This is because Windows client programs do not have the same requirements as Web applications. A Windows client program interface can use multiple decomposition technologies without affecting the performance, this is because the user interface of the Windows client program has a long container lifecycle, while the web application interface is to assemble and transmit the requests of each page by the web browser, this requires a high-performance Layer mechanism to meet the needs of Web applications.

Original article:

Terminology

 

The term "skinning" has different interpretations depending on the audience. at the most basic level, skinning provides you with a static layout but allows you change colors and styles and possibly override images with your own graphm graphics. at the other extreme, skinning can allow you with the capability to customize every aspect of the user interface should t for the actual content. there are obviusly available stages in between these two extremities and your business requirements shoshould drive the optimal solution for your application.

 

Windows clients

 

Skinning techniques have long been popular in Windows client applications. this wowould lead you to believe that it shoshould be a trivial effort to ininform ate the same skinning architecture into your web applications. however, this approach wowould prove to be a tragic mistake.

 

Due to their stateful nature Windows client applications do not have the same requirements as a web application. A skin can be applied to a Windows client application using a wide variety of parsing techniques with little or no performance impact. this is because the user interface in a Windows client application is persistent for the lifetime of the container. compare this to a web application where the entire user interface is assembled and transmitted to the Web browser on every page request. it is quite obvious that an extremely high performance rendering engine is required in a web application to meet these demands.

Dotnetnuke skinning whitepaper translation record:
Dotnetnuke skinning whitepaper translation record (Introduction)
Dotnetnuke skinning whitepaper translation record (term and win Client Program)
Dotnetnuke skinning whitepaper translation record (technical part)
Dotnetnuke skinning whitepaper translation record (definition part)
Dotnetnuke skinning whitepaper translation record (dotnetnuke part)