Dotnetnuke skinning whitepaper translation record (definition part)

Translation:
Definition

Another important aspect to consider in any skin solution is the definition of the skin author. Who will create skin? Which technologies are more suitable for them. What design tools are used in their daily work. The Demand Analysis in this aspect has far-reaching significance for determining how to define the skin.

Although ASP. NET User Control technology provides us with strong core support. They are relatively new technologies on the Microsoft platform. Some design tools ( For example . FrontPage, Dreamweaver, And so on ) You have provided technical support for user controls. However, this concept is still unfamiliar to some professional web designers. Aside from the user control Asp.net This is not a property that is not known to the designer in the server control. Web designers must avoid the risk of disrupting or deleting important server-side controls. Basically, we want web designers to select their own tools to design the skin and keep them isolated from user controls.

 

The conclusion is that the final skin solution should allow web designers to create skin through simple and basic technologies. For the World Wide Web Html Is the most basic general language and widely supported by web design tools. The only problem is Html Is static -- and Web ApplicationProgramDynamic elements.

 

Summarize the above description of the Solution , Allow the designer Html To replace dynamic content. This provides ( Form ) And functions (Fuction) . The application logic is not affected when the skin file is modified. The application logic can also be redefined without affecting the user interface. The only problem is that the additional business layer reduces the performance of the application.

Original article:

Definition

Another very important aspect to consider in any skinning solution is the identification of the skin author. Who will be creating skins? What is their comfort level in terms of technology? What design tools do they use in their business activities? Requirements Analysis in this area plays a large part in determining how skins shoshould be defined.

Although ASP. net user controls provide us with a powerful core technology, they are a relatively new concept and are proprietary to the Microsoft platform. some web design tools (ie. frontPage, Dreamweaver, etc... ) Are now providing embedded support for user controls; however, this concept is still foreign to professional web designers. not to mention the fact that user controls contain references to proprietary ASP. net server controls which shocould not be exposed to web designers. the risk of a web designer mangling or removing critical server controls is not acceptable. ultimately we wowould like web designers to be able to use their tool of choice for creating skins and keep the gory details of user controls separated.

 

As a result the skinning solution needs a method for a web designer to define a skin using the simplest base technology. HTML is the lowest common denominator when it comes to the World Wide Web and has the widest support in terms of design tools. the only problem with HTML is that it is completely static-yet a web application has requirements for dynamic elements as well.

 

Revisiting the token solution described above, it wocould seem useful to allow web designers to include placeholders into their HTML markup which represent dynamic functionality. this provides the cleanest procedure action of "form" and "function ". the skin file cocould be modified without affecting the application logic. the application logic cocould be re-factored without affecting the user interface. the only issue is the performance penalty imposed by this additional layer of separation.

This section is translated by a big chef. I have slightly changed the incorrect word. Who can help me to change the incorrect one :)
Source translation address: dotnetnuke Skin Preparation White Paper (Definition) Chinese Translation

dotnetnuke skinning whitepaper translation record:
dotnetnuke skinning whitepaper translation record (Introduction)
dotnetnuke skinning whitepaper translation record (term and win client part)
dotnetnuke skinning whitepaper translation record (technical part)
dotnetnuke skinwhitning epaper translation record (definition part)
dotnetnuke skinning whitepaper translation record (dotnetnuke part)