Dotnetnuke skinning whitepaper translation record (dotnetnuke part)

Translation:
Dotnetnuke

 

In Dotnetnuke 1.0.0 To 1.0.10 In this version, only a relatively simple skin processing mechanism is available, which allows users to modify Logo , Color and style to generate a website with a low degree of customization. But it does not take long, Dotnetnuke The development team realized that such a mechanism could not meet most of the performance Layer requirements, so they started multiple projects to implement more dynamic skin solutions.

 

Unfortunately, there are many different views on the best solution, and the progress of demand analysis is stuck. Most of these ideas have brought about technical implementation solutions and soon there will be a large number of valuable suggestions on the skin system inCommunityThese ideas have their own advantages and weaknesses. How to choose these solutionsDotnetnukeCoreProgramIt is a very stressful task. In fact, we do not fully accept any solution. We understand that, based on all business needs, we carefully established an imperfect standard and released a solution for testing, and tried to improve it in practice.

 

DOTNET nuke 2.0 The core portal framework was rewritten on a large scale. Initially, only the data access layer and business logic layer were modified, but obviously, the performance layer must be re-checked and rewritten to achieve our goal. Dotnetnuke Now we have a powerful skin system Form ( Form ) And functions (Function) In the next section of this document, we will introduce the detailed technical implementation process of this skin system.

Original article:

Dotnetnuke

 

In versions 1.0.0 to 1.0.10, dotnetnuke contained a very simplistic skinning implementation. it allowed you to modify the logo, colors, and styles to produce a minimally customized website. it did not take long to realize that this implementation did not meet the presentation needs of the general community and varous projects were initiated to implement a more robust skinning solution.

 

Unfortunately, the requirements were slow to evolve as your different people had their own opinions in regards to the optimal solution. most of these opinions took the form of technical implementations and soon there were multiple skinning options available to the community-each with their own specific strengths and weaknesses. an incredible amount of pressure was placed on dotnetnuke to select one of these solutions for each sion into the core. but the fact remained that none of them represented a full implementation, encompassing all of the business requirements we were trying to achieve. and we had to be very careful about releasing a half-baked solution as we understood the issues in creating an incomplete standard and then trying to support it.

 

Dotnetnuke 2.0 represents a ground-up rewrite of the core portal framework. this initially only required Ded the data access layer and business logic layer but it stands to reason that the presentation layer also needed to be overhauled to allow us realize our goals. as a result, dotnetnuke now has des a robust skinning architecture which allows the clean separation of "form" and "function ". the rest of this document focuses on the technical details of the implementation.

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)