Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.basic.visual.misc > #4185

Jvc Winamp Modern Skin Download

Show all headers | View raw

<div>Modern or Freeform skins were originally designed to work with Winamp3. What separates them from the average skin is the fact that they are not confined to the classic rectangular shape. In fact they can be any shape you want them to be and you can put the Winamp control buttons anywhere you want. Some skinners have even added extra buttons that extend the functionality of Winamp right there on the skin. Sounds too good to be true huh? Well these skins require a bit more coding to make and some of the graphics that go into them are quite large. Consequently, Freeform skins may take a bit longer to download from our site and they may take a few extra seconds to load when you switch from one skin to another. But trust me when I say that Freeform skins are worth the extra time and effort. Skin developers have done some incredible things with these skins. You have to check them out.</div><div></div><div></div><div>Changing the skin restored the main window, but back to modern skin it was a one-line-menu again. Research in forums brought up nothing helpful for me, just messing around with the config files didn't help.</div><div></div><div></div><div></div><div></div><div></div><div>jvc winamp modern skin download</div><div></div><div>Download Zip: https://t.co/SOpofeqqUo </div><div></div><div></div><div>We will begin with a simple skin example. I'll give you the essential parts of the skin. In the next section, I'll demonstrate important Winamp3 concepts using this skin. The topics that I'll go over are:</div><div></div><div></div><div>Before you start playing with a skin, you have to know where everything is. Above is a picture of the Winamp directory. If you open that directory ("C:\Program Files\Winamp") with Windows Explorer, it should look pretty similar. The section in blue is the "Skin" directory and the directory that we care about. Within the "Skin" directory, there are sub-directories and files. Each sub-directory and WAL files are a skin. WAL is Winamp3 skin format. Next section talks about how to manipulate it.</div><div></div><div></div><div>Instead of a directory for a skin, you may see only one file with a .WAL extension. Don't worry. WAL (Winamp Abstraction Layer) is Winamp3 skin format. It is basically a zipped file of the skin directory. We do this to save space and to make it easier to distribute the skins. To make changes to that skin, do the following:</div><div></div><div></div><div>Lets take a look at what's in a skin directory. We'll use the "Simple Tutorial" as an example. Keep in mind that other skins may contain other files and directories that are not shown. What we're showing here is the bare minimum example.</div><div></div><div></div><div>Within the "Simple Tutorial" skin directory, there are three items: 1) Skin.xml file, 2) "Player" directory, 3) "XML" directory. The only required file for a skin is the Skin.xml file. It is the file that the Winamp3 skin engine looks for. You can say that it is the entry point for the skin. From that file, all the fun starts. =) I will dissect that file later on.</div><div></div><div></div><div></div><div></div><div></div><div></div><div>The "Player" directory contains all the graphics files for the skin. The files are in .PNG (Portable Network Graphics) format. The "XML" directory is usually where all the XML files are located. Because our skin is relatively simple, there is only one file in that directory.</div><div></div><div></div><div></div><div></div><div>d) #include in XML filesOne more thing I want to go over is the  tag. When the Winamp skinning engine parses this XML file and encounters that tag, it grabs the file specified within that tag and pastes whatever code is inside that file into the current file. So in this example, we're looking at the skin.xml file. The skinning engine will grab player.xml file in the xml subdirectory and paste whatever code that is inside player.xml into skin.xml. This process is recursive. This means that if there's any include file tag inside player.xml, it will get those code also.</div><div></div><div></div><div>These are the graphics that I've used in creating Simple Tutorial skin. One thing to notice is that we like to use PNG file format. Please also use that format too. The graphics files are the parts that we're going to use for our skin. We will define them as elements and link them into our XML code later in order to use them.</div><div></div><div></div><div>The required file for any skin is the Skin.xml file. You can locate this file in your "C:\Program Files\Winamp\Skins\Simple Tutorial" directory. The content of that file is posted above. I'll go over all the parts. I have listed line numbers on the left and code on the right. You can open your version and follow along.</div><div></div><div></div><div>The first line of the Skin.xml file should be the line shown above. The line identifies Skin.xml as an XML file. It is important to remember that you need that line only once in Skin.xml. If you divide your xml into several files, do not include that line in other xml files. Subsequent xml files will be pasted into Skin.xml file by the skin engine.</div><div></div><div></div><div>The WinampAbstractionLayer tag is used to specify which skin version you're following. The version that "Simple Tutorial" skin is made for is 0.8. This tag is used to track compatability. We will keep compatability as long as possible. But sometimes when we introduce a new funcitonality and change an existing one, compatability is broken and we will increment the version number. You will need to update the skin to conform to the new standard. If the skin engine finds your version number is different than the current version, you will see the warning below. However, this does not mean that your skin will no longer work. If functionality that has been changed is not implemented in your skin, you skin will continue to function.</div><div></div><div></div><div>I have discussed functionality above. Note that we're borrowing skins from the Default skin. The only component's appearance we're overriding is the main player. The specification for that is in player.xml (line 14). We'll go over that file next.</div><div></div><div></div><div></div><div></div><div>This section defines all the elements in your skin. This is the part that links the graphics to a "bitmap id" that other XML code can refer to. For example, line 11 links a bitmap id, "blue-player.button.previous", to a graphics component in "player/blue/blue-previous.png" file. That bitmap id is also linked to a gamma group called "Buttons". After linking that object to a gamma group, user can adjust the color variance of that object in the preference menu. Therefore, even if that object is blue right now, you can change it so that it'll appear to be a different color.</div><div></div><div></div><div>As your skin becomes more complex, you will have many elements defined in your skin. It will be useful to break the definitions into different files. Typically, one would define all the elements in each component in separate files. For example, elements in the main player will be in "player-elements.xml" and elements in the playlist will be in "pledit-elements.xml".</div><div></div><div></div><div>If you have already detached the secondary monitor and you cannot move Winamp back to your primary display, you have to edit the Bento skin configuration (typically located at C:\%APPDATA%\Winamp\studio.xnf).</div><div></div><div></div><div>A skin designed with usability in mind (at least one can hope so). My third skin to date but first published on Winamp.com. Graphics and code for this skin were done entirely by myself.</div><div></div><div></div><div></div><div>This skin features 5 custom visualizations (1 is a secret hidden bonus) that have been added to the 2 that come with Winamp for a total of 7 visualizations you can choose from.</div><div></div><div></div><div></div><div>Have Winamp minimized? Enable the Notifier and have Winamp show a tiny message on any corner of your monitor that will let you know what you're currently listening to.</div><div></div><div></div><div></div><div>This and much more! Grab your copy today!</div><div></div><div></div><div>Meh usual glossey chrome crap - Possibly the most under rated skin I've come across, every option is defaulted to off with crappy default color scheme, the number of things you can turn on is awesome. Everything I didn't like I could change and I could turn the gloss off, freaking awesome through sheer options alone. - April 8, 2008 by Hugh McGown</div><div></div><div></div><div>My opinion about this... - This is one of your best skin to my opinion,but there are bugs in it...It stops responding sometimes and Winamp returns to "Winamp Classic" skin.Hope you will check it ,because this skin,and KMS are the best ones!!!(I`m from Romania,that`s why my english my be "corrrupted") - March 24, 2006 by Ustinescu Ionut</div><div></div><div></div><div>Avalon Skin - Its a very nice, clear, unique and well done skin. I work with it nearly a year now and its the opposite of boring. Congrats to Jorge. Brilliant work. - January 10, 2006 by Petra F</div><div></div><div></div><div>Close to perfect - Finally a skin which is extremely functional and streamlined yet good looking and versatile.Although there are many other "cool" skins available so many suffer from the same problems: components like buttons and indicators are just too tiny and almost unreadable.This skin retains a nice modern look and keeps components large enough to be useful and easily readable.It also has many nice options and is quite configurable.This is my everyday skin. Kudos for a stellar skin! - September 29, 2005 by Dean Maynard</div><div></div><div></div><div>Very Tasty! - This skin is by far the best looking and easiest to use. It's multiple color schemes are very nice to have instead of the drab one color skins most others offer. - June 17, 2005 by Kyle Harvin</div><div></div><div></div><div>Nice skin with many details done "right" - I'm a sucker for skins with unique customization options. I especially appreciate being able to configure the auto hide/show of parts of the interface. A good variety of player modes gives it some versatility. Buttons and icons express their functions clearly. What I love most is the Video window. All the controls and info I want for watching videos is contained in a single window. This makes it easier to use, and makes no need for any of the other windows to be open/visible. For some reason I am greatly impressed with the stylish way you were able to fit the video size options and scrolling file info on a single row... on top of the fact that it was collapsable too.Overall, a clean design that's easy to use and easy on the eyes. Only thing keeping me from using this regularly is due to the fact that it's a bit too large for my tastes; maybe with a bit of trimming to the time, vis, and buttons would do the trick. And throwing in a bit more of that contract/collapse & auto-hiding wouldn't hurt either hehe. But if I were to use a skin for watching movies exclusively, yours would be it.Nice work. - May 20, 2005 by Mo Shun</div><div></div><div> df19127ead</div>

Back to comp.lang.basic.visual.misc | Previous | Next | Find similar

Thread

Jvc Winamp Modern Skin Download Finlay Mange <mangefinlay@gmail.com> - 2024-01-21 01:21 -0800

csiph-web