Skin Consortium

Martin, can I release the next build on winamp.com? ClassicPro already use stuff thats skinversion 1.31 (5.51) but I've tested it on Winamp 5.5 and it loads without crash...

Just want to sort the final pictures out and release it so that anyone that want to make their own ones can start.

Will it be okay if I say that its suppose to run on Winamp 5.51(dont know if this is in violation with the beta tester rules )

ClassicPro v0.03

Whats new?
- Live resize like classic skins
- Improved component handling
- Improved Wasabi:Frame
- New shade mode
- Tag Viewer
- Cover rightclick menu + dbl click action
- PL & AVS bottom buttons is now the same size on min size.
- Only one skin included

http://skinconsortium.com/teamsc/classic…sicPro_0.03.exe

First skin where I use relatx="2" & relatw="2"


Short term to do list:
- add wasabi button gfx
- finish shade mode
- add text info on sliders change or buttons pressed
- add mono/stereo/surround code.
- Tidy the colors.xml

Posted a v0.04 version at the winamp.com forums:
http://forums.winamp.com/showthread.php?s=&threadid=282523

Download v0.04 Here:
http://skinconsortium.com/teamsc/classic…sicPro_0.04.exe

Quad, still need to add a few stuff and to test it I'm gona make a lame winXP cPro skin just to make sure I didnt overlook something.

Have to add gfx for the component buttons for the big AVS.... and maybe the big video too.

Anyone can later add another type of cPro skin if they have the time. Can maybe use the new readRGB methods to place the buttons. Just think how easy it will be to make a skin then. We can package a few types of cPro engine skins.

Asked Mike to make a custom vis for the big bento cPro skin, but dont think he have the time atm... If anyone is up to it and have time feel free. Was think of little llamas.(You can use as many frames as you like... skin will read the height and know how many frames you have...

Will post a new version of cPro tonight... Just a few cosmetic stuff... just added added a way to hide the menu, added the reader for the classic Vis and a few other stuff.

Busy with the following cPro skins:
- cPro - Big Bento
- cPro - Classic Winamp
- cPro - WMP 11
- cPro - Windows XP

Will post them all tonight too.. but they are far from finished... the best one besides the bigbento one atm is the WMP11... need help to finish them.

Okay now for the real reason for this post:

Want to know what the other admins think about changing this section into a public one. I want to do the following:
- Change name to Winamp ClassicPro Skins
- Move just after the modern & classic in the mainlist
- Add a thread for each of the skins that I have on my pc thats unfinished... Skin in progress - blabla...
- Add a sticky with notes on how to edit the cPro skins.
- And add keep this thread as a sticky for discussions about cPro
- Add a thread with all the downloads for cPro with version history.

The cPro WMP11 skin is looking, even if I have to say so, pretty cool. Will post l8r.

As I said before, anyone can l8r add their own 'engine' to the pack. Would be cool to have a non sui one too. Where all the first cPro engine stuff is in classicPro\engine\ anyone can just make their own type of engine by just adding another engine folder to the install with their own stuff. Offcoarse by anyone I meen anyone at SC

Will be ready tonight with the new version stuff.

Here is the latest cPro installer, required for all the skins starting with cPro.

Download ClassicPro v0.06 (279kb)

Whats new?
- If the mainmenu bitmap is a certain pink, it wont be displayed. Just one pixel is checked. See the WinXP & WMP11 & WaClassic skins for a demonstration of this.
- Added albumart.png... this can be any size and will be resized.
- More minor tweaks

Hey, if it doesnt slow the skin down(noticeably) then why not. Dont know how you'll change the colors. Will it just change all of the colors of the skin? Most of the skins posted so far have no alpha blending so the colors for the buttons for example cant be changed because it contains parts of the player background. Can implement conventional colorthemes, but I think it might slow the skin down and make skinning difficult because you then have to work with antialias edges and stuff like that.
Was thinking of adding lets say 20 themes that change all the colors, with all layer in one colorthemegroup... but dont think that might work.... maybe just have a brigher, darker,..... themes. But if RGB can work with it why not. (Dont know what/how you want to implement it basicly.. but if you think it could work)

Would be cool if Martin could add a way change system colors from maki... then I could add a bitmap that could be used to read all the system colors for the skin... would really make it allot easier.

ClassicVis: Yes want to add the timeline vis... and a few menu options.. but dont want to make it too complicated.. just basic settings. The timelinevis will have to work of the colors found in the mainframe.png file... so no animation file ... Dont know if this will slow things down.

Another thing that I havent tried before that I think you might be able to help with:
I want to make the bands for a mode thin and then hide ever second line so that it look like a hi def classic vis. Is it possible to region out a certain part of a bitmap so that I can paste it over the <vis object?


Will work more on the engine in the next build.

SloB I have a Job for RGB.

I want to include component buttons for the big views (tab views).
Will use the gfx from Big Bento's component buttons
They are a little transparent and mostly greyscale.

But I dont want to make to much things to skin for the skinners so I was wondering if it would be posible to just change the colors of this grayscale buttons to what ever color the skinner want. Colors can be read in via bitmap(using the new RGB value Map reader.

Gonna add component buttons for the avs, video & playlist tab. Also added the browser so can change those colors too because look the same.

Let me know what you think.

How do I 'cut' each second line of the thin band <vis so that it looks like a high def vis? Do I have to cut out the layer under the vis and paste it over it? Or is there an easier way.