Dotnetnuke skinning whitepaper translation record (Introduction)

Original article:

Introduction

 

"Traditionally, professional web design companies rely on static html pages to get their profits. however, with the emergence of business portal web applications, customers quickly learn the benefits of dynamic pages. To meet new requirements, web designers need to pay close attention to the development of these new technologies. The skin system in dotnetnuke allows professional web designers to create a web site that seamlessly integrates with the underlying portal application and develops a powerful function that visually meets customers' needs ."

 

The term "skinning" comes from a method that separates application logic, content, and presentation layers in software engineering and provides users with easy management. This form and function extraction is sometimes called a dual expression mode. The advantage of the skin system is that the application logic is separated from the web page layout, and can be independently designed and modified. In this way, a software developer and a web designer can cooperate with each other without worrying about interfering with their work.

 

ASP-the primary reason for its popularity in Web rapid development is that ASP scripts can be inserted into HTML tags to make static html a dynamic web page. This feature makes it possible to quickly develop ASP applications and create a dynamic page associated with a database (or other external data sources) to create a powerful web application.

 

However, the simplicity of this kind of use is costly. In most ASP websites, ASP scripts and HTML tags are messy, making it difficult for them to read and maintain. This problem is often exposed to web designers who want to modify the website's art interface. The most typical change from content presentation to ASP scripts is that web developers and web designers must work together to ensure the integrity of the changes during the modification process. This leads to more efforts, more time, and more cost to achieve the goal.

 

The ultimate goal of a skin system is to use a template to separate the content and presentation layer from the application logic. A powerful and intelligent skin system is used to collect content, presentation layers, and application logic and ultimately generate a product, this dual expression model allows developers and designers to have their own identities when maintaining the website. The advantage of this mode is that the release project can greatly reduce the time and workload.

 

Of course, skin systems increase the complexity of Web applications while providing such convenience. When a large number of files are merged to generate a single page, the Web application performance may decline, at the same time, developers must have good quality to ensure that the presentation layer and content are well expressed and precisely positioned in their script code. The above two problems can be mitigated through technology and a reliable skin system.

Translation:
Introduction

 

"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 communicate with this new demand, web designers need to become acquainted with the opportunities presented by these new semantic ical 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 variable action 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 certificate 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 uugly 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 received acted from their script code. both of these items can be mitigated through the use of technology and a solid skinning architecture.

Dotnetnuke skinning whitepaper translation record:
Dotnetnuke skinning whitepaper translation record (Introduction)
Dotnetnuke skinning whitepaper translation record (term and win Client Program)
Dotnetnuke skinning whitepaper translation record (technical part)
Dotnetnuke skinning whitepaper translation record (definition part)
Dotnetnuke skinning whitepaper translation record (dotnetnuke part)

E is not very good. Please point out a lot of silly errors or inappropriate points :)