WMC - Winamp Modern Classic (Template)

[garetjax]

After much folly trying to create a modern skin and running afoul of very many problems with maki code and similar. I decided to start over; I am creating a Classic Skin that is simplistic and written from the beginning in the modern skin wrappers.

What this means is that 99% of the skins ever submitted could easily be converted to winamp 5 engine; simply buy placing my skin.xml in your folder then converting your images to png. That is all.

Though, realistically you could then extend your skin for the feature you want easily or change the bounds of the box to be whatever you want. I feel this is a better approach to getting a skin to be a modern one without all the erroneous waste of maki.

here is my progress to date:
http://garet-jax.deviantart.com/art/...0%3A1349652282

I will get this done and at submission this will be entirely FFE (FREE FOR EVERYONE); No attribution or reference required. I figure it will be my gift.

Thank You,

[garetjax]

So, what is going on with this...

Well, I have diverged or forked my code...we now have 2 versions of the template.

1. Classic Base Loader (Loads BMP Graphics for an older skin)
2. Classic Updated Loader (Loads PNG Graphics and has missing buttons available crossfade and such).

There are other changes but, I wanted to have the fullest support for either and make it dead simple to publish your skin without having to code a whole lot of shyte. Here is another of my code updates:

Classic Updated Skins Now Have
cbuttons.png that includes the eq/pl/shuf/rep/crossfade/winamp.menu as well as an active/hover state for them all.
Note: All Pixel Bugs are removed.

Classic Base Loader
Nothing Unique here (no changes). Though you could use bmps and go 'updated' The fact that its working is interesting enough.
The Classic Base Loader does not load shared lines...you may want to compensate for this or just go updated again.

If you have comments suggestions and etc. Let me know.

[LuigiHann]

This seems really promising.

I wonder how much trouble it would be to make it scalable in some way, to have the same layout as a classic skin but at let's say double the resolution, so I could then clean them up to make HD remakes of my older skins. Would be cool.

[pjn123]

Posted reply on DA too.. An Xml function not used allot and that was designed(not 100% complete last time I checked) was the <images/> one.

http://wiki.winamp.com/wiki/XML_GUI_...3Cimages.2F.3E

Is there a preview available?

[garetjax]

Yes, I use the images array based selector for the volume and balance. They work pretty well; as for a preview not quite yet. I am still working through the seperation logic between bmp and png skin loads.

WMC.xml and WCL.xml
(Winamp Modern Classic) and (Winamp Classic Loader)

WMC - Is a converted winamp classic with pngs/alphas/transparencies and missing images for buttons in modern.

WCL - Is just the bmp loads of a winamp classic skin. No Changes. ~

I may release them as seperate skin templates just to keep things simple and keep to that one xml file to rule them all idea; but we shall see soon enough.

I do know that on WMC based skins there are some changes:
text.png (isn't used on my skin) but a remarked xml entity is setup for usage.
monoster.png (is completely removed, though I may yet code it in with a remark) I use songinfo.png.
eqmain is a slide in container rather than a windowed object and as such I have removed the frame boundary and the titlebar in my skin. Though again I have remarked entities to enable it normally.

There are a lot more but, I am not quite ready to speak to features that are yet to be fully complete.

Of note: I am using 0 addl scripts. I have put that as a limit on the skins themselves. With any luck i can keep it that way.

[garetjax]

Looking For Some People to assist me on the
Winamp Classic Loader and Winamp Modern Classic.

Due to the massive amount of coding required I figured I'd reach out and see who else may be willing to work with me.

There are a few rules if you are willing to help:

Absolutely, no other scripts can be used to load into the xml.
Only a single xml file can be used to load the skin(s).

Everything must be pixel perfect and fully functioning. I am completing the main at the moment for both loaders. I am somewhere around 50-60% complete for both loaders.

If your interested (and of course just curious) give me a shout and we can talk.

[garetjax]

FYI (I have decided to seperate them into 2 templates):

For the WCL.XML File there is currently 317 Lines of xml
- Uses SkinnersAtlas as the base
- Only BMPs are in the XML (though, easily couuld be swapped for png)

For the WMC.XML File there is +/- 608 Lines of xml.
- Uses B3L8TD as the base
- PNG's and Vector Based Graphics are in the XML
- Vector Graphics only partially working.
- I may have to include a maki for the vector based graphics functionality. Though, I'm testing it at the moment. ~

[garetjax]

We got it...!!!!!!!!!!!

[garetjax]

I've done it...just a few little loose ends to tie up now. I have begun my first Winamp skin using the new templating system!

[Victhor]

Although I´m not really excited about replicating the classic skin, I´m really looking forward to this for the potential it has. I don´t fully understand the hole process, but sounds great if at some point I can experiment with it! .

[garetjax]

If that was why I was doing it then sure; would kinda suck. Though, realistically I'm doing it to learn and to hopefully bridge the gap. I know The Plague originally started a similar project sometime ago and has all the functional requirements to support 99% of the features to my best bet. I am looking to extend the benefits of a great deal of features from the WA5 Skin Engine to the Winamp Classic Skinning area. I believe that by doing this it will allow for classic skinners to make some nice skins with limited coding required and getting all the benefits of classic type skins. Though, I am also scared that this will open up Skinner Templating Applications again and we end up with craptastic image skins with shitty button overlays.

I guess that is what you get when you make things simple (and you get some badass skins as well).

[garetjax]

At very least it will make me a coder and designer. Of Which FYI - I can compile and make maki scripts to interact with the Winamp Engine now.

[garetjax]

I've updated the WMC/WCL Loader now, the damn eq finally is functionally. Sheesh that took it out of me. Though, I may have to rewrite the vertical slides for the eq...I don't want to do maki; so if anyone knows the easiest way to do a vertical slider based of a set of images (we have the eqmain to use) which sux cus of the height =63

Not easily divisible.


Oh here is what I've got - it is okay...for the moment, some areas are still to be worked on

(uncompressed folder size = 324k)
(compressed folder size = 164k)

Not bad for a full graphic png winamp 5 base skin and it loads crazy fast with all windows open. ~

[garetjax]

Alright, anyone who is following this thread...

I am ready to start test the first beta. At present I am only supporting the Main and Eq Windows and this is specifically for WMC skins. Slightly upgraded versions of classic skins. The layouts are the same with some minor adjustments.

Note: I have tested that all basic functions work and that all areas are skinned to my best ability. There are some additions that are not yet documented so, if you use this template be aware that I may change some features going forward until I am near a release.

[garetjax]

Here is the WCL (Winamp Classic Loader)
---------------------------------------
You can use this as a simplified loader for bmps and just change a few set of graphics where you need to apply alpha/transparency or etc. ~

Again this is in test only at this point. I am currently working on the playlist/ml. Presently both WMC/WCL work with the WASABI based playlist and media library windows only. I will be building all the other windows in time.

Thank You,

P.S.
If you are testing these please post on the winamp forums about your experience or let me know of fixes. Again this is basic functionality only, and I will be adding seek status', volume status, balance status, button click status, optional crossfade, about window and more soon.

[garetjax]

Found a problem with the eq

[Victhor]

Cool!! A beta! I 'll try it as soon as I get to my desktop PC!

[pjn123]

You can use this object to get the wa2 type song ticker(just change the params):

PHP Code:

<SongTicker id="m.st.ticker" 
        fitparent="1"
        showlen="1"
        rightclickaction="trackmenu" dblclickaction="trackinfo" align="right"
        color="Player.SongTicker.Text" fontsize="16" valign="top" antialias="0"
/> 


Sorry for the scforum reply about the eq - For some reason I thought that the eq slider start with green in the middle (like the pan one)

I see if you put the bmp's in the root folder some generic stuff gets skinned already. Knew about the pledit scroll button that you can skin this way but not the other stuff.

The next/open button doesn't look right?

I see what your going for now. Like that you are not trying to do a 100% copy and are trying to add some UI refinements that the skinners can remove if they want.

When the modern skin engine was designed they should have made sure that all the current wa2 skin stuff can be done without scripts being used. Not everyone want to edit script to create a skin. Just setting your computer up to compile a script is already a big job.

As for this template, another idea might be to collect a few XUI objects from various sources and include them in your folder for the skinner to use. Feel free to include any relevant xui objects in cpro(just not centrosui) (C:\Program Files (x86)\Winamp\Plugins\ClassicPro\engine\xui). Azenis 2 also have some if I remember right. Theres more here too. For example using the <SC:Text /> object you can create your own custom text field that change with the song:

PHP Code:

<SC:Text
   x="172" y="31" w="-281" h="15" relatw="1"
   fontsize="18"
   myText="%artist% - %title% (%length.time%)"
   dblclickaction="trackinfo"
/> 


This might be easier for beginners to understand because they don't have to think about scripts because they can now just edit the custom xui object's param like they would have edited a normal internal xml Winamp object.

A folder with lots of scripts from the forums and skins will also be helpful if skinners want to add something extra.


But anyway... just an idea, might not be what your going for here

Great work so far!

Cheers!
PS: Hitting F5 in the template skin shows whats possible with load times in Modern Skins

[garetjax]

Yes I am trying with all my experience to make this thing come about, I am wanting to expand on this. It is taking a lot of thought and patience. I am unsure of whether I will include addl scripts beyond those already defined unless, of course I find no other method. I think cpro is good but, for me is overkill. Though, I must admit now that I am doing similar work I can understand why you guys went to Sui. My current headache is the playlist...ugh.

[Victhor]

The thing turned really "technical" for me (lot of code), so I´m not following the most part of it, I can not help, but count on me for an eventual skin with this system!

[garetjax]

Ideally I want to have a system flexible enough to accept scripting but, doesn't require coding at all. I want to have a fully represented classic base with minimal scripting to have the 3.0 engine build a framework for classic skins. Something I believe should have been done from the beginning. Though again I can understand why it wasn't. To that end itiky will not be setup w/ a lot of Xui though I'm not saying it won't use them or not allow for it.

[mike-db]

Just saw this thread, checking it out now.

Seems the timer doesn't work, but it looks great! Haven't tried skinning anything yet but I'm excited to jump in.

[garetjax]

Sorry Mike-DB,

I am currently spending my time debugging and working with the WMC Template more than the WCL. I did notice that the WCL Template has a timer bug. I will get on that when I am more complete with the playlist on the WMC Template.

Thank YOu,

[garetjax]

Due to complexity - I decided to break up the xml. While efficient it was way to hard to read the damn thing. And took forever to find what wanted. If you want it this way; let me know I can do both.

Here is the layout structure at the moment.
<Skin Folder>
- skin.xml
- <graphics>
- * All Skin Graphics are to be located here
- <scripts>
- * All Foreign Scripts are found here w/ both compiled and un-compiled sources
- <xml>
- * All Layouts for Windows are found here
- main.xml
- eqmain.xml
- pledit.xml (All Positions
- ml.xml
- * All Graphics Definitions are here (Width, Height, X & Y of Image within existing image etc.)
- elements.xml (All Graphic Defines)

Additionally, I have updated a few things. The eqMain now is an ordinal reference to the position based on a float:
-127 to 0 to +127 the elements are in reference to the location of the slider position. (i.e. -14 to 0 to +14 - Rounding may cause the first position or last pos to be skipped)


More (From Peacemaker):
Contributed the Playlist coding and a few notes from him regarding things we want to do:
1. updating the scrollbar background or scrollbar button graphics.
2. working out any button commands. (we will need to make the button stacks in maki first) then assign the buttons commands if we can find them, otherwise, it wont be the same as wa2 and would be like the standard wa5 buttons, = not what you want.
3. reading from pledit.txt file to get the colour codes for altering the playlist props.) *In-Progress
4. shade mode stuff.
5. Separate the xml into different files for easy editing. (Completed)

[mike-db]

Bugs and small things are to be expected! I'm just so darned excited for this! Glad to see that PM is on board as well.

[garetjax]

pjn123 - has been contributing as well.

We are definitely working on getting this released. As we improve our scripting and features that were found in the original; you should expect to be able to do at least that, but with additional things that will be found in commented sections/uncommented depending on which skin you are playing with

[garetjax]

https://github.com/garrjo/WMC_WCL_Template/branches

If you want to contribute or propose changes - you can do so yourself ~

[garetjax]

https://github.com/garrjo/WMC_WCL_Template/

To get the latest updates:

1. Updated Playlist (to grid)
2. Updated Scripts (Doublesize for playlist now)
3. Status Script built and compiled
4. Attrib.m pulled from modern library.
5. Updated playlist oridinal positions (graphics)

Current work:

Making grid actually resize...idk but, it isn't going well yet.
we will see ... of note peacemaker has a fork going to do the full playlist in classic guise. Whereas the current branch is with a grid that does not support the pl stacks. Once this is done it will be put into both branches.

[garetjax]

https://github.com/garrjo/WMC_WCL_Template/

Current Commit Includes Updates to the playlist. ~

[pjn123]

Hi Garetjax

I posted a new playlist in the SC forums.
Might be easier if you use that as the starting point

It's a shame that we can't replicate the add/rem/sel/misc button popups with actions

[garetjax]

Yes, I have tried everything to get the action states to interact with the static items for the playlist actions. They just aren't allowed...sadly.

Ahh, well...everything must evolve at some point. Nice job btw:

To Get a Current Version:
https://github.com/garrjo/WMC_WCL_Te...ive/master.zip

To Get review our project:
https://github.com/garrjo/WMC_WCL_Template/

[garetjax]

Updated to include source maki/m files and changes to the songinfo ticker. Pause, Stop, Play and Resume will now update the ticker. I am working on the ticker showing volume/balance/shuff/repeat as well.

I am also working on the following:

1. plcolorize.maki - will import text from playlist into array that will then be parsed into a hextorgb conversion for usage on textual objects on a container/windowholder.

2. genex.maki - in progress. (:bwuahahah

I've got other things that are coming... as well. With any luck it will the closest you can get to a winamp classic skin without it being so. I've also, tested a few things with the WMC Skin (ADO Elite). In general you can 'adjust the shape of the skin' without any issue and move things wherever you want them of course.

You can imagine the simple flexibility you get with this sort of idea. I've also begun writing alternative vu/avs settings for the main.xml

Options Being Considered are:
1. L/R VU Meter
2. L/R Analog Meter (Needles)
3. Standard VIS
4. Standard and Mirrored VIS
5. Inverted VIS
6. Flame VIS (hehhahahah) Special ~