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

翻译：

定义

在任何一个皮肤解决方案当中要考虑的另一个重要方面是皮肤作者的界定。谁会创建皮肤？什么技术更适合他们。在他们的日常工作中使用什么样的设计工具。在这一方面的需求分析对决定如何的定义皮肤有深远的意义。

尽管ASP.NET的用户控件技术给我们提供了较强的核心支持，他们是微软平台相对较新的技术。一些设计工具(如. FrontPage, DreamWeaver, 等 ) 已经提供了对用户控件技术的支持。但是在这一概念对于一些专业的网页设计人员还很陌生。抛开用户控件中包含了ASP.net 服务器端控件中不为设计人员所知的属性这点不说。网页设计人员打乱或删除重要的服务器端控件的风险是一定要避免的。基本上我们希望网页设计人员选择自己的工具设计皮肤并保持和用户控件分离。

 

结论是最后的皮肤解决方案应该能让网页设计人员通过简单和基本的技术创建皮肤。 对于万维网来说HTML是最基本的通用语言，并被网页设计工具所广泛支持。 唯一的问题是HTML是静态的——而web应用程序要求动态的元素。

 

总结以上对解决方案的描述 , 允许设计人员在 HTML 中插入标志符来代替动态内容会很有效。 这就提供了对表单（ form ）和功能 (fuction) 的很好的抽象。皮肤文件在修改的时候不会影响应用程序逻辑。 应用程序逻辑也可以在不影响用户界面的情况下重新定义。唯一的问题是额外增加的业务层会降低应用程序的性能。

原文：

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 should 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 many professional web designers. Not to mention the fact that user controls contain references to proprietary ASP.NET server controls which should not be exposed to web designers. The risk of a web designer mangling or removing critical server controls is not acceptable. Ultimately we would 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 would seem useful to allow web designers to include placeholders into their HTML markup which represent dynamic functionality. This provides the cleanest abstraction of “form” and “function”. The skin file could be modified without affecting the application logic. The application logic could be re-factored without affecting the user interface. The only issue is the performance penalty imposed by this additional layer of separation.

此节由大厨师翻译，我稍微改了一下错字，谁也帮我前面改改不通顺的地方：）
原翻译地址：DotNetNuke 皮肤制作白皮书 （定义部分）中文翻译

DotNetNuke Skinning Whitepaper 翻译记录：
DotNetNuke Skinning Whitepaper 翻译记录(简介部分)
DotNetNuke Skinning Whitepaper 翻译记录(术语与win客户端程序部分)
DotNetNuke Skinning Whitepaper 翻译记录(技术部分)
DotNetNuke Skinning Whitepaper 翻译记录(定义部分)
DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)