DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)

翻译  ：

DotNetNuke

 

在DotNetNuke 1.0.0到 1.0.10版本中，仅具有一个相对简单的皮肤处理机制，它允许用户通过修改网站的LOGO，颜色和样式来产生一个自定义程度比较低的网站。但不用多久，DotNetNuke开发组就意识到这样的机制无法满足大多数的表现层要求，于是启动了多个项目来实现更具有活力的皮肤解决方案。

 

不幸的是，在最佳解决方案的看法上具有很多不同的观点，需求分析的进度因此而停滞不前。大部分这些观点都带来了技术实现方案并且不久又有大量的关于皮肤体系的有价值的建议在社区中被提出——这些观点都有他们自己的优点和弱点。如何选择这些解决方案作为DotNetNuke 的核心程序是一件具有非常大压力的事情。实际上我们并没有全盘接受任何一个方案，围绕着所有的业务需求，根据我们理解，我们很慎重的建立了一个未完善的标准并发布了一个用于测试的解决方案，并尝试在实践过程中去完善它。

 

DotNetNuke 2.0对核心门户框架进行了一次大规模的重写，最初仅对数据访问层和业务逻辑层进行修改，但显而易见的对于表现层也必须重新检查和改写以达到我们的目的。 DotNetNuke 现在拥有了一个强大的皮肤体系，实现了表单（form）和功能(function)的分离，在这个文档接下来的部分，我们将介绍关于这个皮肤体系的详细技术实现过程。  

原文：

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 various projects were initiated to implement a more robust skinning solution.

 

Unfortunately, the requirements were slow to evolve as many 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 inclusion 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 included 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 includes 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 翻译记录：
DotNetNuke Skinning Whitepaper 翻译记录(简介部分)
DotNetNuke Skinning Whitepaper 翻译记录(术语与win客户端程序部分)
DotNetNuke Skinning Whitepaper 翻译记录(技术部分)
DotNetNuke Skinning Whitepaper 翻译记录(定义部分)
DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)