1
Skins / Re: Winamp Skins Twitter bot
« on: February 12, 2018, 02:44:47 AM »
Don't get me wrong, "bad" and "crappy" skins are welcome, as long as they are interesting. Only "boring" skins don't make the cut.
Latest restricted WACUP beta release is build #18980 (April 24th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18980 (April 24th 2024) (x86 only)
NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.
Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Skins / Re: Winamp Skins Twitter bot
« on: February 05, 2018, 03:17:22 PM »
Originally I thought I could get away with just posting random ones, but as you point out, there are too many bad/boring ones.
So, I do a manual review process where I only approve “interesting” skins.
So, I do a manual review process where I only approve “interesting” skins.
3
Skins / Winamp Skins Twitter bot
« on: January 24, 2018, 03:54:11 AM »
I made a Twitter bot which tweets a screenshot of a Winamp skin, along with a link to the skin (and a link to try the skin on Winamp2-js) a few times a day.
You can see it here: https://twitter.com/winampskins
Feedback welcome!
You can see it here: https://twitter.com/winampskins
Feedback welcome!
4
Archive / Re: Winamp. In your browser.
« on: January 24, 2018, 03:52:40 AM »
Hey Joe,
I have the playlist window fully working now (a few tiny things I still want to clean up before I release it, but it's fully working). One easy thing to try would be for 1001skins to provide a link to Winamp2-js which included the URL of the skin in the hash. This is the approach I'm using for https://twitter.com/winampskins
For example: https://jordaneldredge.com/projects/winamp2-js/#%7B%22skinUrl%22%3A%20%22https%3A//s3-us-west-2.amazonaws.com/winamp2-js-skins/Pizza_Hut_v5.wsz%22%7D
You can read more about the syntax here: https://github.com/captbaritone/winamp2-js#advanced-ussage (note you may have to url encode the bit after the #.
This would require setting up the correct allows-origin headers for the skin files, let me know if that's difficult to do in your setup.
If you can get the headers working, it would mean you could add a "preview" or "try" link for a skin just by generating the correct URL. Might be an easy place to start.
Let me know what you think. Feel free to reach out here, or via email: jordan@jordaneldredge.com
I have the playlist window fully working now (a few tiny things I still want to clean up before I release it, but it's fully working). One easy thing to try would be for 1001skins to provide a link to Winamp2-js which included the URL of the skin in the hash. This is the approach I'm using for https://twitter.com/winampskins
For example: https://jordaneldredge.com/projects/winamp2-js/#%7B%22skinUrl%22%3A%20%22https%3A//s3-us-west-2.amazonaws.com/winamp2-js-skins/Pizza_Hut_v5.wsz%22%7D
You can read more about the syntax here: https://github.com/captbaritone/winamp2-js#advanced-ussage (note you may have to url encode the bit after the #.
This would require setting up the correct allows-origin headers for the skin files, let me know if that's difficult to do in your setup.
If you can get the headers working, it would mean you could add a "preview" or "try" link for a skin just by generating the correct URL. Might be an easy place to start.
Let me know what you think. Feel free to reach out here, or via email: jordan@jordaneldredge.com
5
Archive / Re: Winamp. In your browser.
« on: August 26, 2017, 01:33:10 AM »
Hey, Jordan (Winamp2-js author) here! Thanks for the kind words about the project. It’s been great fun. I've actually been thinking a fair bit about the use case of using Winamp2-js for automating the process of taking screen shots. With headless Chrome it really shouldn't be too difficult. In fact I hacked together a little eight line script using Chrome’s [Puppeterr](https://github.com/GoogleChrome/puppeteer) library and was able to get a pretty good looking screenshot of an arbitrary skin. I want to do a bit more work to get it working to the point where you can take the screenshot in any state you wish. This might require some minimal refactoring to the existing code base.
If I did get this working robustly, how would people want to use it?
Download/install/setup and then use from the command line?
Web interface where you can drag in a skin and get an png?
Web based API where you post a skin and get a URL to a png?
Javascript library which you could call with a path to a skin to get a promise for a png?
One possible long term goal would be to make a skin gallery website where you could browse via (generated) screenshots, and then click that screenshot to preview the skin in your browser. (If anyone has interest in the project and wants to help, let me know!)
Another possible project would be an online skin explore which would allow you to drag in a skin and see all the sprites split out and labeled. (Again, let me know if this interests you).
I have the equalizer window nearly working, you can follow the project on GitHub [here](https://github.com/captbaritone/winamp2-js/projects/1)
and I have the chrome UI for the playlist window working, but that one is going to require a much larger effort, since the whole media chain has to be updated to be aware of multiple files. For the purposes of screenshotting skins, it would probably be possible to start with the UI for the playlist first, as that will be much easier.
If anyone is interested in contributing (the project is React+Redux and fairly well organized) I’d be happy to help find interesting tasks to work on. Currently I’m working on how multiple windows snap together when you drag them around.
I’m not putting a huge amount of time into this project these days, but I am continuing to chip away at it bit by bit. I probably work on it at least an hour or two each week. Of course having other contributors would probably increase my interest
Thanks again,
Jordan
If I did get this working robustly, how would people want to use it?
Download/install/setup and then use from the command line?
Web interface where you can drag in a skin and get an png?
Web based API where you post a skin and get a URL to a png?
Javascript library which you could call with a path to a skin to get a promise for a png?
One possible long term goal would be to make a skin gallery website where you could browse via (generated) screenshots, and then click that screenshot to preview the skin in your browser. (If anyone has interest in the project and wants to help, let me know!)
Another possible project would be an online skin explore which would allow you to drag in a skin and see all the sprites split out and labeled. (Again, let me know if this interests you).
I have the equalizer window nearly working, you can follow the project on GitHub [here](https://github.com/captbaritone/winamp2-js/projects/1)
and I have the chrome UI for the playlist window working, but that one is going to require a much larger effort, since the whole media chain has to be updated to be aware of multiple files. For the purposes of screenshotting skins, it would probably be possible to start with the UI for the playlist first, as that will be much easier.
If anyone is interested in contributing (the project is React+Redux and fairly well organized) I’d be happy to help find interesting tasks to work on. Currently I’m working on how multiple windows snap together when you drag them around.
I’m not putting a huge amount of time into this project these days, but I am continuing to chip away at it bit by bit. I probably work on it at least an hour or two each week. Of course having other contributors would probably increase my interest
Thanks again,
Jordan
Pages: [1]