WSZ Files - Revision history

Culix: Reverted edits by Iseficibuw (Talk) to last version by Explorer09

2010-11-30T03:28:58Z

Reverted edits by Iseficibuw (Talk) to last version by Explorer09

Iseficibuw at 05:12, 24 November 2010

2010-11-24T05:12:17Z

Explorer09: {{ClassicSkin}}

2010-07-24T09:12:39Z

Hydrargyrum: /* WSZ History */ verbosity; convoluted grammar

2009-02-23T23:03:30Z

‎WSZ History: verbosity; convoluted grammar

Tarik: Protected "WSZ Files" [edit=autoconfirmed:move=autoconfirmed]

2008-09-25T13:02:06Z

Protected "WSZ Files" [edit=autoconfirmed:move=autoconfirmed]

Tarik: Unprotected "WSZ Files"

2008-09-24T17:12:34Z

Unprotected "WSZ Files"

Tarik: Protected "WSZ Files": All pages locked during Beta except for Article & FAQ page. [edit=sysop:move=sysop]

2008-09-22T21:19:33Z

Protected "WSZ Files": All pages locked during Beta except for Article & FAQ page. [edit=sysop:move=sysop]

Wahdahtahdammie at 19:53, 27 August 2008

2008-08-27T19:53:38Z

New page

Creating a Classic Skin: [[The Base Skin]] --> [[Main|Paint the Main Window]] --> [[Equalizer|Paint the Equalizer Window]] --> [[Playlist|Paint the Playlist Window]] --> [[Mini-browser|Paint the Minibrowser Window]] --> [[AVS|Paint the AVS Window]] --> [[For_Winamp_2.9/5.x|Paint the Winamp 2.9/5.x Windows]] --> [[Creating Custom Cursors|Create Custom Cursors]] --> [[Editing the Configuration Files|Edit the Configuration Files]] --> [[WSZ Files|Compress to .WSZ format]] --> [[Submitting Your Skin to Winamp.com|Submit to Winamp.com]]

==Winamp Skin Zip Files (WSZ)==

The last step you need to do before unleashing your Skin on the world is to convert it to the WSZ format. How do I do that, you ask? Just follow the following steps:

#With your trusty zip compression tool of your choice, zip YOUR skin's folder (not the Winamp "Skins" folder) into a .zip file.
#Rename the new file's extension from .zip to .wsz.
#Test it by removing your skin folder, then placing your .WSZ into the Winamp "Skins" folder.
#Run Winamp, then press Alt-S to access the Skin browser. If you see your skin, then everything worked correctly.
#That's it! Pat yourself on the back, then take the next step and submit it to Winamp.com.

==WSZ History==

A Winamp skin is composed of 45 files. Most of the files that create a skin are .BMPs (a very common image file type) and a few text files. When skin support was originally implemented, an artist would have to create those skins and place them into a subdirectory of the Winamp Skins folder (Usually located in C:\Program Files\Winamp\Skins folder).

This all started becoming a mess due to the fact that not all of the skin developers were creating subfolders when compressing their skins into a ZIP file for distribution. When an end-user uncompresses the files to the Winamp Skins folder, it would at times overwrite other skins. As a solution, we implemented the functionality into Winamp to read the .ZIP files directly. What would happen is an end-user would simply place the .ZIP file into their Winamp Skins folder and when using the Skin Browser in Winamp (ALT+S) the skin magically appeared and loaded if selected.

This did clean up the mess, however, a new problem then surfaced. The .ZIP file format is a very widely used compression type and Winamp was just one of the many dozens of programs available to utilize it. We wanted users to be able to double click the Skin ZIP file and have Winamp automatically install and load the skin. How do we do that without associating Winamp as the default program for handling skins? Rename the file extension.

We simply took all those compressed skins ending with the .ZIP and renamed them to end with .WSZ (Winamp Skin Zip). This allowed us to stay with the standard Winamp .ZIP files and not have to convert the thousands of skins available for download on the Internet. Any skins that are submitted to our site, ending with .ZIP or .WSZ, are automatically renamed to end with a .WSZ before published.

Why do all this you ask? The answer is simple. We wanted to make it so that Winamp would automatically load the skin when a user clicked on a link to download a skin from Internet Explorer as well as Netscape Navigator. We also wanted to make it so that if a user actually had downloaded the .WSZ file, all they would have to do is double click it to install it.

Exactly what happens at this point? Well, when a person installs a .WSZ file what happens is Winamp just copies the file to the Winamp Skins folder so that it can be handled correctly. You can also manually move the .WSZ file into your skin directory and Winamp will recognize it just as well.

@@ Line 1: / Line 1: @@
 {{ClassicSkin}}
@@ Line 6: / Line 5: @@
 The last step you need to do before unleashing your Skin on the world is to convert it to the WSZ format. How do I do that, you ask? Just follow the following steps:
-#With your trusty zip compression tool of your choice, zip YOUR skin's folder (not the Winamp &quot;Skins&quot; folder) into a .zip file.
+#With your trusty zip compression tool of your choice, zip YOUR skin's folder (not the Winamp "Skins" folder) into a .zip file.
 #Rename the new file's extension from .zip to .wsz.
-#Test it by removing your skin folder, then placing your .WSZ into the Winamp &quot;Skins&quot; folder.
+#Test it by removing your skin folder, then placing your .WSZ into the Winamp "Skins" folder.
 #Run Winamp, then press Alt-S to access the Skin browser. If you see your skin, then everything worked correctly.
 #That's it! Pat yourself on the back, then take the next step and submit it to Winamp.com.
@@ Line 14: / Line 13: @@
 ==WSZ History==
-A Winamp skin is composed of 45 files. Most of the files that create a skin are .BMPs (a very common image file type) and a few text files. When skin support was originally implemented, an artist would have to create those skins and place them into a subdirectory of the Winamp Skins folder (usually located in &lt;code&gt;C:\Program Files\Winamp\Skins&lt;/code&gt;).
+A Winamp skin is composed of 45 files. Most of the files that create a skin are .BMPs (a very common image file type) and a few text files. When skin support was originally implemented, an artist would have to create those skins and place them into a subdirectory of the Winamp Skins folder (usually located in <code>C:\Program Files\Winamp\Skins</code>).
 This started getting messy, because not all of the skin developers were creating subfolders when compressing their skins into a ZIP file for distribution. When an end-user uncompressed the files to the Winamp Skins folder, it would at times overwrite other skins. As a solution, we implemented the functionality into Winamp to read the .ZIP files directly. Then, an end-user would simply place the .ZIP file into their Winamp Skins folder; when using the Skin Browser in Winamp (ALT+S), the skin magically appeared and loaded, if selected.

@@ Line 16: / Line 16: @@
 ==WSZ History==
-A Winamp skin is composed of 45 files. Most of the files that create a skin are .BMPs (a very common image file type) and a few text files. When skin support was originally implemented, an artist would have to create those skins and place them into a subdirectory of the Winamp Skins folder (Usually located in C:\Program Files\Winamp\Skins folder).
+This did clean up the mess.  However, a new problem then surfaced: The .ZIP file format is a very widely used compression scheme and Winamp was just one of the many dozens of programs available to utilize it. We wanted users to be able to double-click the Skin ZIP file and have Winamp automatically install and load the skin. How do we do that without associating Winamp as the default program for handling skins? Answer: Rename the file extension.
-This all started becoming a mess due to the fact that not all of the skin developers were creating subfolders when compressing their skins into a ZIP file for distribution. When an end-user uncompresses the files to the Winamp Skins folder, it would at times overwrite other skins. As a solution, we implemented the functionality into Winamp to read the .ZIP files directly. What would happen is an end-user would simply place the .ZIP file into their Winamp Skins folder and when using the Skin Browser in Winamp (ALT+S) the skin magically appeared and loaded if selected.
+We simply took all those compressed skins ending with the .ZIP extension and renamed them to end with .WSZ (Winamp Skin Zip). This allowed us to stay with the standard Winamp .ZIP files and not have to convert the thousands of skins available for download on the Internet. Any skins that are submitted to our site with filenames ending with .ZIP are automatically renamed to end with a .WSZ before published.
-This did clean up the mess, however, a new problem then surfaced. The .ZIP file format is a very widely used compression type and Winamp was just one of the many dozens of programs available to utilize it. We wanted users to be able to double click the Skin ZIP file and have Winamp automatically install and load the skin. How do we do that without associating Winamp as the default program for handling skins? Rename the file extension.
+Why do all this, you ask? The answer is simple. We wanted to make it so that Winamp would automatically load the skin when a user clicked on a link to download a skin from Internet Explorer, as well as Netscape Navigator. We also wanted to make it so that if a user actually had downloaded the .WSZ file, all they would have to do is double-click it to install it.
-We simply took all those compressed skins ending with the .ZIP and renamed them to end with .WSZ (Winamp Skin Zip). This allowed us to stay with the standard Winamp .ZIP files and not have to convert the thousands of skins available for download on the Internet. Any skins that are submitted to our site, ending with .ZIP or .WSZ, are automatically renamed to end with a .WSZ before published.
+What happens then? Well, when a person installs a .WSZ file, Winamp just copies the file to the Winamp Skins folder so that it can be handled correctly. You can also manually move the .WSZ file into your skin directory and Winamp will recognize it just as well.
-−
-Why do all this you ask? The answer is simple. We wanted to make it so that Winamp would automatically load the skin when a user clicked on a link to download a skin from Internet Explorer as well as Netscape Navigator. We also wanted to make it so that if a user actually had downloaded the .WSZ file, all they would have to do is double click it to install it.
-−
-Exactly what happens at this point? Well, when a person installs a .WSZ file what happens is Winamp just copies the file to the Winamp Skins folder so that it can be handled correctly. You can also manually move the .WSZ file into your skin directory and Winamp will recognize it just as well.

← Older revision	Revision as of 13:02, 25 September 2008
(No difference)

← Older revision	Revision as of 17:12, 24 September 2008
(No difference)

← Older revision	Revision as of 21:19, 22 September 2008
(No difference)