Add ability to change skin on player

[jeffpaul]

Is your enhancement related to a problem? Please describe.
This is probably best left as a block setting and not something we'd need to worry about supporting on the site front-end. We should be able to test with available skins in the Winamp Skin Museum, but will want to determine if the way the webamp player works is that it expects skins to be in the Winamp Skin Museum or if they can be provided from within the same domain that the webamp player is rendered on (i.e., the site this plugin will be installed on and thus whether the plugin needs to be bundled with the skins or if the skins can be selected / linked from the Winamp Skin Museum).

Describe the solution you'd like

• figure out how to switch a skin within the current player
• figure out whether skins have to be on the remote Winamp Skin Museum, have to be available on the same domain the webamp player is rendered on, or both (or something else perhaps?)
• figure out how to allow a custom skin to be displayed on the player if we're unable to get our custom skin added to the Winamp Skin Museum

Designs
See #1

Describe alternatives you've considered
Only provide initial support for a single, default skin.

Additional context
n/a

[dkotter]

I've added a block setting where you can paste in any valid skin URL:

These URLs come from going to https://skins.webamp.org/ and then clicking on any skin. You then copy the resulting URL and paste that into this new field.

This is then parsed on the FE to load the correct skin:

Not exactly sure if this is the approach we want to go with or not, so look at this more of a proof of concept that we can change if desired.

[jeffpaul]

@dkotter that's awesome, nice work! The next question will be how to potentially load a custom skin if we're unable to get the one that @melchoyce is helping to create published on the skins.webamp.org site?

[dkotter]

Couple options that come to mind:

1. Right now if no skin URL is entered, we just load whatever default skin comes with the player. We could make the custom skin the default instead and bundle that skin with the plugin
2. If we don't want it to be the default, we could still bundle the skin but then have a toggle to turn that skin on (and probably hide the skin URL input)
3. We could go fancier and have an upload field allowing any custom skin file to be used. We would have to add support for .wsz files to WordPress but this would allow any custom skin to be used. Not sure it's worth the effort and also doesn't solve how other people will download this custom skin to use in the first place

[jeffpaul]

It looks like we may be able to submit our custom skin via https://skins.webamp.org/upload/ and then link to that similarly to linking to other skins in the library.

[jeffpaul]

We could have some skins as options in a single select at launch with the basic winamp skin as default, but figure out a graceful UX way to allow folks to select other skins in the library. Though a simple URL field also generally achieves that as well.

[jeffpaul]

I'd like to see us have a small set of skins easily selectable, either as a dropdown with their names displayed or (ideally better) thumbnails of each selectable, and then an advanced option to enter the skin URL (current functionality). The subset of default skins would be the 4 in the first list in the description of #1 (with ideally a custom skin crafted in that issue to be added later). Obviously if someone is passionate enough about another skin(s) being a default option then I'm open to that as well.