WB Skin Library....Why all the Zip files?

Used to be when you downloaded a WB skin from the WB library, you got just what you expected....a *wba file and nothing more and the skin would auto-install, unless you set the *wba extension not to in Windows file properties. Now folks are uploading *zip files that include additional files, for many reasons, and I'm sure mostly for completing the user's WB experience with that particular skin. It all can be avoided though and the library can get back to just having *wba files again if folks just do a couple of things....

Fonts - SKS (SkinStudio) allows for the inclusion of fonts in a skin and also installs them for the user so there is no need to add them separately in a zip.

Wallpaper - If the wallpaper is a *bmp, SKS allows for it to be included and applied within the *wba file. Otherwise I think best practice would be to make it a separate download and provide a link to it in your description or better yet, if the wall won't pass moderation, build a winstyle theme with the skin and the wall.

Other Stuff - DX widgets or whatever else have a separate library here and again just provide a link to it in your description.

Winstyle Themes - If you really want to include a whole bunch of stuff with a WB skin, build a separate Winstyle Theme. That way folks have a choice. They can either get just the WB skin or they can get the theme with all the extras (wallpaper, widgets or whatever else) and you get more downloads that way.

That's just my 2-cents and getting the WB library back to just *wba's also makes it easier for new users to customize.
7,570 views 8 replies
Reply #1 Top
A very good 2 cents Essencay, if they want to include wall as .jpg to keep file size down can it be include in .wba in a folder or in a zip. I think have downloaded WB's this way before.
Reply #2 Top
Good post S&K. Was just about to upload a new skin with wallpapers zippedup in a zip file. Saw your post and changed to just the wb.
Reply #3 Top
I see your two cent and raise you two.
I like it when I can just click download, wait for it to finish, then click that little tooltip that appears in the systray to install it. So easy, so simple.
Why not make it so you can only upload wba files to the WB skin section?
Reply #4 Top
SNK - sometimes .wba files do not self install due to SP2 problems.
Reply #5 Top
kona....I know that that's not the issue here
Reply #6 Top
sometimes .wba files do not self install due to SP2 problems


For me with IE, will not self install on download, when download to disc, open folder, double click the .wba it installs. If was a zip would have to rename or extract. When downloading IE treats .wba as .zip, when saved to folder it is a .wba.
Reply #7 Top

The .wba association is lost if you don't unload WindowBlinds before installing SP2. It goes without saying you should unload all programs before installing SP2 - I wonder how many people have...

Reply #8 Top
Here's just a couple of examples of what I mean....
https://www.wincustomize.com/ViewSkin.aspx?SID=1&SkinID=5020&LibID=1 zip file containing *wba file, folder full of fonts and a readme file.

https://www.wincustomize.com/ViewSkin.aspx?SID=1&SkinID=5013&LibID=1 zip file containing *wba file, six wallpapers and four DX widgets.

Not picking on anyone, I've got DSL now, so I really don't care how large the files get or what's in them. It's just less confusing for someone new or when you are trying to help someone new, especially if all the *wba files they download show up as *zip files, when you're only dealing with one type of file in each library