ClassicPro v2.01 (28/02/2013)

[pjn123]

@Aminifu - The r-click functions is just there because it was the easiest way to add something. For example the beatvis - Cant click it because then the seeker change. Also didn't want it as a setting somewhere else because thats not how cpro1 worked. But added a tooltip to inform the user. Should add it at the few other hidden features too (not that there are too many).

[warning - boring stuff coming]The tooltip in the seeker for the beatvis was actually not as easy as it looks. Had to code it specially so that it looks like a normal tooltip. Normally when your mouse enter an object a tooltip can be shown by just using the tooltip="xx" xml param. But here the whole seeker is the object and you can only rightclick in the middle part to change the beatvis.

Can possible add more right-click/mouse wheel functions if it useful (dont have any ideas though). The right-click menu's on buttons like stop, prev, next are pretty useless FOR ME but I'm sure there might be that one person somewhere that will need it hehe.

@Victhor - A skin shouldn't need too much documentation but just a few pointers/tips should help. Maybe I should do a short youtube video sometime.

@moderator - Can someone with powers please update the first post by replacing it with post 153

http://forums.winamp.com/showpost.php?p=2901790&postcount=153

Thanks!

[Aminifu]

Hi pjn123,

As you see, Victhor reminded me that Winamp has supported automatic r-click functions for some time, so it is me who has failed to keep up with things. I'm one of those few who find context menus useful, even on stop, prev, next, etc.

As for the beatvis, isn't it usually the case that when you change one thing to please someone (moving the seek bar to the top), it causes a problem somewhere else. Good that you have the skill to work it out.

I had disabled tooltips (guess its time to turn them back on for a while), but I see that the one on the beatvis shows up anyway. It is a good way to alert users of new functions, but once they know about them will there be a way to turn them off. I hate to nit-pick, so that will be the last one. For a while, anyway.

For an app like Winamp, it's usually fun to fool around and learn new things about it. The cPro engine does bring new things to the game. I'm sorry I took so long to try it.

[Aminifu]

Hi pjn123,

It's too bad that the idea behind 'MusicShow' didn't catch on. I think it would be way cool to add the 'Skin Focus' feature that is in the 'MusicShow' skin to cPro2.

What do you think? Is it even possible?

[pjn123]

The focus is just a gray background that could maybe be implemented with a widget for cpro. But have been a while since I had MusicShow on my pc... must probably install it again and just double check how it was done.

[Aminifu]

The focus is just a gray background that could maybe be implemented with a widget for cpro. But have been a while since I had MusicShow on my pc... must probably install it again and just double check how it was done.

Yes, its like the effect you can get with a UAC prompt. This request is more of a wish list kind of thing to be looked into later. Please don't let it interfere with your more important 'To Do List' items for cPro2.

[DrO]

@moderator - Can someone with powers please update the first post by replacing it with post 153

http://forums.winamp.com/showpost.php?p=2901790&postcount=153

Thanks!

should be done now (having pm'd a moderator would have gotten it done sooner as no one really monitors these threads).

-daz

[pjn123]

@DrO - Thanks

[iron2000]

Currently slowly working the cPro2 XUI into my cPro-minimal skin.

It seems like the Web Reader and Media Library objects are taller then the side drawer.
Their bottom edges are not aligned.
I can overwrite the height of the Web Reader through sendparam but can't do for Media Library as it has no h parameter.

Is this a design of cPro2?

[pjn123]

Hi iron2000

Glad to hear it (about the new skin in the pipeline that is )

I can't see what your talking about (maybe my skin here dont show it that good) - Can you maybe post or PM me a screenshot of the problem. If it isn't aligned then it will be fixed for the next version so you wont have to hack it. Also planning my own proper skin with the cpro2xui object to test drive it and make sure there isn't any bugs. This will hopefully take shape next week.

[iron2000]

Compared to cPro, cPro2 is a bit more restricted (but in another sense less images to change).
If only there are more ids for the objects to open up overwriting via sendparams.

minimal with cPro2 XUI is pretty much skinned up (but theres still a lot of cleanup to do), one problem left is that in cPro2 both main status buttons and drawer status buttons are mapped to sui_comp_buttons.png.
In cPro both have their own png.

The buttons I use for the main status buttons doesn't look good on the slim drawer status bar.
So I tried ways to make the slimmer status bars thicker.

I tried to change the height of some of the components (e.g make the playlist object shorter).
Worked for drawer Visualization but not the sidebar's.
Didn't work for drawer playlist, the playlist did become shorter but I can't touch the rect background as it has no id (wanted to make it higher as the status bar is a different color).

It would be best if theres a 'switch' somewhere to allow the drawer status buttons to have their own png when the skinner needs it. Or maybe the drawer status buttons will follow another png when it is present in the directory.

[pjn123]

cPro2 was always going to be a bit more restricted for the skinner maybe but I think there is still enough room for a skinner to manipilate the UI enough to create some very cool skins. I'm thinking of the ClassicPro.xml file that now includes more power. Since the infoseek area is one of the most important make or brake parts of the skin you can move the text you see there around if you need to or change the size or style off coarse. Further more the seeker don't have to overlay the complete infoseek area. I did a quick mock up in the sc forum of a possible cpro2 bento skin that can maybe demonstrate this:

http://forums.skinconsortium.com/index.php?page=Thread&postID=26020#post26020

Secondly cpro2 isn't suppose to be a replacement for cpro1 skins. We just experimented with a new layout that I think is very easy to work with especially since I like the fact that I can easily grab the seeker and the skin also resize to very small sizes now.

While I was busy with the new version I split the new layout side and the sui section side of the code that wasn't possible to do in cpro1 skins. This will probably be more useful for experience skinners like you that really like to do allot of modifications to the original cpro1 layout. There might someday be more cpro2 xui skins than plain cpro2 skins :P (I'll also try to demonstrate how easy it is with my first cpro2 xui skin)

Now since this is still in beta there is probably still a few bugs in the new cpro2 xui object but I'm currently building my own skin to testdrive the whole progress. With your feedback we'll also be able to "iron" the bugs out

As for the status buttons. This was done to save a few resources and to save the skinner some trouble in doing the same buttons twice.
Are you suggesting that the main area, bottom drawer, side mini area and side playlist each have their own statusbar + button gfx? Or just main, drawer+mini and playlist?
If you want you can maybe send me a screenshot of the skin like it is atm and then one where you changed the skin in photoshop to illustrate what you want to achieve at the end. Maybe I can then look at it and see what the best way will be to tackle this.

PS about objects id's:
I know some objects don't have id's. I only added id's normally if there was a script that worked with that object. Also in cpro2 more of the objects are placed dynamicly (mostly due to the fact that the frame_player.png can have any height).

If you want you can change the source code in the xml files to add id's to objects you would like to access. I'll then include your changes in the next build? But hopefully after your illustration above there will be a easier way to do things since another objective of cpro2 was also to not require skinners to do so much mods to achieve small things like a shadow or different images for a button light (for colortheme purposes).

[iron2000]

So far theres no problem with the infoseek stuff, using only the XUI component I can design the other elements around it as I like

The only restrictive area is within the XUI component, to get it to fit the design of the outside elements.
I need some time to take screenshots, tidy up my thoughts and maybe offer some suggestions on the status buttons.

[iron2000]

I've setup a thread for the skin at the SC forums and posted screenshots there.
Got to put it down by today or I'll procrastinate :P

[pjn123]

ClassicPro v2.01 Final (28/02/2013)



We’re proud to announce ClassicPro 2 is finally ready and is now out of beta stage!

Thanks for all the help by email, forum and pm’s. If you have more ideas (and feel that we might have forgotten a few of yours) feel free to bring it up in the comment section below.
Download ClassicPro 2.01 here




Then remember to check all the new ClassicPro2: SUI skins. These type of skins allows the skinners to create their own custom layout but let cPro take over the single user interface using the XUI object. More info here.

Currently there are 3 such skins in development/available:
(cPro2 - divx by MerTcaN | cPro2 - Winamp for Mac Sync by pjn123 | cPro2 - minimal by iron2000)


What's new since previous beta release?

Version 2.01 Final (28 Feb 2013)

• cPro 2
• New: Now also support preset window positions (shift+F9-12 to set)
• Updated: cPro2__Aluminum v1.3 (new themes and lots of other improvements)
• Fixed: If Winamp load on zero volume, volume jumps up (sc_mute)
• Fixed: More buttons with transparent bits don't always work
• Fixed: Classic vis doesn't always go to thin bands on small width
• Fixed: File info viewer layout broken if you hide first tag
• Fixed: Playlist search toggle overlay doesn't hide on small widths
• Fixed: Alignment of status bar buttons (thx Mertcan)
• Fixed: Playlist search box background color
• Fixed: Button fade shows wrong hover image when you toggle button with shortcuts
• Improved: File info viewer layout order now same as Winamp
• Improved: File info viewer added option to use smaller size
• Improved: File info viewer resource optimization
• Changed: Tab icons now have 3 states (see cPro2 - Aluminum)
• Changed: Gammagroup of the Open/Close drawer buttons changed ("n.sui.buttons")
• Changed: Widget Manager header image
  
• cPro 1
• New: Right-click on main menu button to disable menubar (maybe more options later)
  
• cPro 1&2
• New: Added more options to multibutton (Winamp bolt right-click)
• Fixed: About current skin crash on newer Winamp builds
• Fixed: Skin notifier sometimes no longer appearing
• Improved: Quick Playlist now use screen size to calculate menu height
• Improved: Widget Manager notifications now only once globally and not per skin
• Improved: Now Playing widget now have right-click options menu (v1.01)

[Aminifu]

Hi pjn123,

Thank you very much for the fixes and additions to cPro 2.01. Everything is working great on my system, except for 1 thing.

Right clicking on the main menu button does not disable the menubar on the cPro 1 skins that I use on occasion (cPro_Bento and cPro_MPxi_remix). Instead the right click activated the function of a 3rd party plug-in that I use. The cPro_MPxi_remix skin does not have an actual main menu button, but if I right click in the upper left hand corner I get the same response.

This general purpose plug-in is called "Find File On Disk" (written by DrO). It opens Windows Explorer to the folder(s) containing the currently selected song file(s) and selects it(them) in the folder(s). It can be activated with the "Ctrl+F" hotkey or via a command added to the Playlist Editor's context menu.

The stranger thing is that this right click behavior continued even after I deleted the plug-in and it also works this way with the new cPro2_Aluminum v1.3 skin too. However, the hotkey does not work and the context menu command is not present when the plug-in is not installed. So is this a bug, an undocumented feature, or a previously reported feature that I'm not aware of.

The find-on-disk feature is useful, but it is unexpected to have it activated this way.

The ability to remove the File, Play, Options, View, and Help menu buttons (on skins that use them) is a minor issue, imo. Something that would be nice to have, but not a must have option. In addition, if the cPro_MPxi_remix window is made narrow enough, these buttons are not displayed anyway. I assume all cPro 1 skins, with these buttons, work that way.