“传统上,专业的网页设计公司依赖于静态的HTML页面获取他们的利润.然而,随着商务门户web应用程序的出现 , 客户迅速的了解到动态页面带给他们的好处。为了适应新的需求,网页设计者需要时刻关注这些新技术的发展。DotNetNuke中的皮肤系统可以让专业的web设计者创造出与底层门户应用程序无缝结合用户界面,开发出具有强大功能而在视觉上又满足客户需要的web站点。”
术语 “Skinning(皮肤)” 来自于软件工程中将应用程序逻辑、内容与表现层分离出来而提供给用户方便管理的一种方法。这种表单和函数的提取有时候被称为双重表现模式。皮肤系统的优点在于应用程序逻辑和web页面外观版式是分离的,而且可以各自单独的设计以及修改。这样,一个软件开发者和一个网页设计师就可以不用担心妨碍对方的工作而进行合作。
ASP – 它作为一个web快速开发工作流行的首要原因实际上是由于asp脚本可以插入到HTML标记中使得静态的HTML成为动态的web页面。这个特性使得快速开发asp应用程序和建立一个与数据库(或其他外部数据源)关联的动态页面进而创建一个功能强大的web应用程序成为可能。
然而,这种使用上的简易性是有代价的,大多数ASP网站中,ASP脚本和HTML标记杂乱的混杂在一起,使得他们难以阅读甚至难以维护。这种问题通常在web设计者希望修改网站的美工界面时露出了他们的丑恶嘴脸。至从内容表现被包含在ASP脚本当中,最典型的改变是在修改过程中必须由web开发者和web设计者共同努力以确保修改的完整性。这导致要达成目标需要更多的努力,更多的时间和付出更高的代价。
皮肤系统最终要的目标就是使用模版将内容以及表现层从应用程序逻辑中分离出来。一个强大智能化的皮肤系统是用来集合内容、表现层以及应用程序逻辑而最终产生一个产品,这种双重的表现模式让开发者和设计者在维护网站的时候具有各自独立的身份,这样做的优点是在发布项目的阶段可以大量减少时间和工作量。
“ Traditionally, professional web design companies have relied on static HTML web sites for a substantial portion of their revenue. However, with the emergence of economical portal applications, the consumer has quickly become savvy to the benefits offered by dynamic web sites. In order to cope with this new demand, web designers need to become acquainted with the opportunities presented by these new technological advancements. The skinning architecture in DotNetNuke allows professional web designers to create stunning user interfaces which integrate seamlessly with the underlying portal application to produce a powerful, yet visually appealing customer web site.”
The term “Skinning” refers to a software architecture which provides you with a manageable way to separate application logic and content from its presentation. This abstraction of “form” and “function” is sometimes referred to as a two-tiered presentation model. The advantages of skinning are that application logic and web page layout are separated and can be designed and modified independently. A software developer and a web page designer can collaborate without the risk of interfering with each others work.
One of the nice things about ASP - and one of the primary reasons for its popularity as a rapid web development (RAD) tool - is the fact that ASP script can be inserted into regular HTML markup to turn otherwise static HTML content into intelligent web pages. This feature makes it possible to quickly write ASP applications that build web pages dynamically from a database (or other external data source), and to create powerful web applications.
However, this ease of use comes with a price. Most ASP web sites contain a mangled spaghetti of intermingled HTML markup and ASP script, making them hard to decipher and even more difficult to maintain. This problem most commonly rears its ugly head when web designers need to alter the user interface. Since the presentation attributes are embedded in the ASP script, changes typically require a joint effort between a web developer and a designer to ensure the integrity of the modification. This ultimately results in more effort, more time, and higher cost.
Skinning involves the use of "templates" which separate presentation and layout attributes from application logic. An intelligent skinning engine is then used to assemble the artifacts into a final product. This two-tiered approach affords both developers and designers a fair degree of independence when it comes to maintaining a web site, and can substantially reduce the time and effort required in the post-release phases of a development project.
However, skinning also introduces some complexities to your web application. The process of merging multiple files into a single page can lead to serious performance degradation. Not to mention, developers must be well educated to keep the presentation details of layout and appearance abstracted from their script code. Both of these items can be mitigated through the use of technology and a solid skinning architecture.