Dotnetnuke skinning whitepaper translation record (skin package part)

Translation:
Skin pack

 

A skin package or container package consists of a large number of files that make up a complete skin:

 

• *. Htm, *. htmlFile-used in the skin upload mechanism*. AscxFile.

• *. Ascx File -- Skin Mechanism Html File must be formatted and pre-compiled to produce user controls used to define the skin.

• *. CSSFile-the style sheet file corresponding to the skin.

• *. GIF ,*. JPG ,*. JPEG ,*. PNG -- graph files in the skin.

• *.*-- Other resource files used in the skin (note that you must allow upload in the extended name settings of the website upload file .)

 

A skin package can contain multiple skin files, which allows designers to create multiple series of skins with the same picture but with slightly different la S. Obviously, when you make some modifications to the regular presentation layer, the more skin files you need.

 

Most package systems use the document list concept to identify various files in a package and define additional package attributes. Although this concept is conducive to the performance of raw data, it also introduces additional creation and maintenance work. For product maintenance, our main point is: simply compressing these files into a compressed package is more advantageous than introducing a list.
Original article: 
Skin package

 

A skin or container package is comprised of multiple files which constitute a complete skin:

 

• *. Htm, *. html files-Abstract skin definition files which will be processed by the skin Uploader to create an *. ascx File

• *. Ascx files-skin definition user controls which are precompiled in the format required by the skin engine.

• *. CSS files-styles sheets related to skins

• *. GIF, *. jpg, *. JPEG, *. PNG-supporting graphics files

• *. *-Any other resource files required for your skin (Please note that the allowable file extensions are secured by the host file upload extensions setting)

 

 

A skin package can contain multiple skin files. this allows you to create skins which leverage the same graphics but vary slightly based on layout. obviusly the more skin files you have in a package, the more maintenance will be required when you wish to make a general change to the presentation in the future.

 

most" packaging "schemes employ the concept of a manifest file to identify the various files encoded in the package and define additional package attributes. although this concept has benefits in terms of the metadata capability, it also represents another artifact which needs to be created and maintained for the life of the package. maintaining our product focus, we felt the simplicity of zipping a group of files into a package far exceeded the benefit provided by introducing a Manifest requirement.

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-big Cook translation)
Dotnetnuke skinning whitepaper translation record (dotnetnuke part)
Dotnetnuke skinning whitepaper translation record (Overview)
Dotnetnuke skinning whitepaper translation record (file organization part-big Cook translation)
Dotnetnuke skinning whitepaper translation record (page processing part)