16
Latest restricted WACUP beta release is build #18916 (April 18th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #18916 (April 18th 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]
17
Archive / Which skin should be the default on new WACUP installs? (Decison made 16th Oct)
« on: September 19, 2018, 04:21:11 PM »
As the title of the thread says, I need some input on which skin should be the default on new WACUP installs as we'll soon have 4 possible skins to choose from when making a WACUP install. I really don't know which one should be the default as there's numerous arguments depending on how we want to aim WACUP going forward or just what people's expectations are in terms of usability vs performance & resources (i.e. classic is much lligher-weight compared to a feature complete modern skin & whether a few seconds to load the skin is acceptable or not)
The skins we'll have are:
There are also some other possibilities to be considered...
The first is on a clean WACUP install (which would also cover updating an existing 5.666 install) we essentially force a skin to be selected as per the attached first_run_skin_selection_mock.png image (the layout & wording is just an initial spin on the idea so don't be too harsh
)
The second is we go with a default skin and instead have a 'pimp my skin' section on the installer skin selection page as per the attached pimp_the_skin_mock.png image which would possibly cycle through the screenshots of some of the other skins present so you can see what the others may look like.
Maybe both options make sense to implement or just the one (possibly the first option seems to be a better fit from the discord conversation that led to this thread & some comments in the BBM thread).
So over to you as I would probably go with classic & the forced skin selection on first run but my view on this will not be the final decision & it's what the majority vote or even what is a better suggestion that comes out from this that will end up being implemented I'd also appreciate knowing why you think whichever option is the way to go or not as that definitely helped with the update system thread to make the feature work well.
-dro
The skins we'll have are:
- 2.x base skin (with WACUP tweaks)
- Big Bento Modern (BBM)
- Big Bento / Bento (Winamp default from 5.5 to 5.666)
- Winamp Modern (Winamp default from 5.0 to 5.35)
There are also some other possibilities to be considered...
The first is on a clean WACUP install (which would also cover updating an existing 5.666 install) we essentially force a skin to be selected as per the attached first_run_skin_selection_mock.png image (the layout & wording is just an initial spin on the idea so don't be too harsh
)The second is we go with a default skin and instead have a 'pimp my skin' section on the installer skin selection page as per the attached pimp_the_skin_mock.png image which would possibly cycle through the screenshots of some of the other skins present so you can see what the others may look like.
Maybe both options make sense to implement or just the one (possibly the first option seems to be a better fit from the discord conversation that led to this thread & some comments in the BBM thread).
So over to you as I would probably go with classic & the forced skin selection on first run but my view on this will not be the final decision & it's what the majority vote or even what is a better suggestion that comes out from this that will end up being implemented
I'd also appreciate knowing why you think whichever option is the way to go or not as that definitely helped with the update system thread to make the feature work well.-dro
18
Wishlist / Feature Requests / Windows 8/10 native notification toast support
« on: September 17, 2018, 01:42:11 PM »
Mainly leaving this as a reminder for myself to add support to WACUP to use the Win8 & newer toast notification system as a way to have 'modern' toasts for now playing changes (any possibly other things) which will work irrespective of the skin being used for those who like those sorts of things
From looking at the docs, it's a bit convoluted to do it as part of a classic windows program but it can be done (probably something for my sunday night r&d session over the next few weeks).
-dro
From looking at the docs, it's a bit convoluted to do it as part of a classic windows program but it can be done (probably something for my sunday night r&d session over the next few weeks).
-dro
19
Preview Build Discussion / WACUP Installer Command-line Options
« on: July 30, 2018, 02:38:17 AM »
To help do specific things during install either for WACUP's needs or if you want to script updates yourself, WACUP installers provided from 2018 onwards provide the following command-line options which can be chained together (e.g. /IAGREE /SKIPDIR /SKIPSKIN).
These are handled case-insensitively so /iagree works the same as /IAGREE or /iAgReE (unless stated otherwise). Finally if you don't specify any command-line options then the full installer experience will be provided so consider these options as advanced and that you know how to use the command-line.
/IAGREE - skips the welcome, license & changelog page (if applicable) during install to save your fingers a few clicks & implies you agree to installing what has been provided
/PORTABLE - selects the portable install mode (settings stored in the install folder) by default instead of a normal install (which stores the settings on a per-user basis)
/SKIPSKIN - skips the user specific stage of the install process where the current skin can be selected
/SKIPDIR - skips showing the directory selection page so the default install folder or the path specified via the /D=<path> switch is the one used
/S - runs the installer silently whch will assume a default full install including location (see below) of where it's installed, etc
/D=<path> - sets the default installation directory and this must be the last parameter used in the command-line and must not contain any quotes, even if the path contains spaces. Only absolute paths are supported.
-dro
These are handled case-insensitively so /iagree works the same as /IAGREE or /iAgReE (unless stated otherwise). Finally if you don't specify any command-line options then the full installer experience will be provided so consider these options as advanced and that you know how to use the command-line.
/IAGREE - skips the welcome, license & changelog page (if applicable) during install to save your fingers a few clicks & implies you agree to installing what has been provided
/PORTABLE - selects the portable install mode (settings stored in the install folder) by default instead of a normal install (which stores the settings on a per-user basis)
/SKIPSKIN - skips the user specific stage of the install process where the current skin can be selected
/SKIPDIR - skips showing the directory selection page so the default install folder or the path specified via the /D=<path> switch is the one used
/S - runs the installer silently whch will assume a default full install including location (see below) of where it's installed, etc
/D=<path> - sets the default installation directory and this must be the last parameter used in the command-line and must not contain any quotes, even if the path contains spaces. Only absolute paths are supported.
-dro
20
Wishlist / Feature Requests / MOVED: Uninstaller option for keeping prefs
« on: July 02, 2018, 02:57:47 PM »21
Skins / Are you feeling festive...? Skins can help...
« on: December 14, 2017, 09:19:44 PM »
As it's coming up to the festive time of year, why not get in the mood with your Winamp / WACUP install with this classic mod of the Winamp Modern skin from http://koopa.meggamusic.co.uk/holidayskin/ (note It doesn't use the layout / settings from an existing Winamp Modern skin install so you may need to move windows back to where you want them)
Also if you know of any other festive themed skins then post them below as I'm sure there's some classic ones out there for everyone to enjoy (or not
).
-dro
Also if you know of any other festive themed skins then post them below as I'm sure there's some classic ones out there for everyone to enjoy (or not
).-dro
22
Archive /
« on: April 21, 2017, 02:13:58 AM »
Today marks the 20th birthday of Winamp and I've put up a new blog post (https://getwacup.com/blog/index.php/2017/04/20/happy-20th-birthday-winamp/) covering some of those 20 years with our favourite player and how things have changed from it's humble beginnings.
So have some
So have some
23
General Discussion / What's your preference on keeping versions up-to-date ?
« on: January 19, 2017, 05:22:18 PM »
One of the pains that Winamp had was too many keeping using older versions instead of wanting / being able to use newer versions.
Now as we know the WACUP beta builds expire after a time (which is being refined over the builds released so far) as a means to keep active use on the current builds to minimise support burden (e.g. not having to re-test multiple versions).
From the beta sub-forum thread about the expiration issue, one thing that has come up which I'm really not sure about and that's whether for eventual release builds if a similar thing would be acceptable (e.g. when a newer release build comes out, should it effectively push the new version to be used in some manner) or is it best to accept a fragmented user base as the norm and leave the control of updating in the user's hands so as not to be evil ?
Thoughts and suggestions below please. As I think for beta builds it's ok to have them expire, but for release builds it makes me feel uneasy.
-dro
Now as we know the WACUP beta builds expire after a time (which is being refined over the builds released so far) as a means to keep active use on the current builds to minimise support burden (e.g. not having to re-test multiple versions).
From the beta sub-forum thread about the expiration issue, one thing that has come up which I'm really not sure about and that's whether for eventual release builds if a similar thing would be acceptable (e.g. when a newer release build comes out, should it effectively push the new version to be used in some manner) or is it best to accept a fragmented user base as the norm and leave the control of updating in the user's hands so as not to be evil ?
Thoughts and suggestions below please. As I think for beta builds it's ok to have them expire, but for release builds it makes me feel uneasy.
-dro
24
Archive / Forum Updated + Getting Back To Normal
« on: January 10, 2017, 04:17:27 AM »
Quick FYI on a few things...
I've finished updated the forum software to the latest version (2.0.13). There shouldn't have been any issues with this (the update went cleanly) but am mentioning it just incase.
I've missed some of the replies / PMs that have been sent over the last few days as the notification emails haven't always been being sent out. I'll look into it fully in the morning though post update and from a quick re-check it seems to be ok again
So apologies over my slowness in reply to some (not helped with unrelated things that have been taking up my time over the last few days).
Also after the mess that was the festive period and computer and real life stuff that's been going on over the last 3 weeks or so, today (Tues 10th) I can now get back on with resuming full WACUP development work (as well as getting the missed blog posts, etc finished off and posted) so things are still alive and most things should be sorted over the next day or two.
The next beta build, I think it's going to be some point next week (w/c 16th and not this week as I'd first hoped) but I'm hoping to provide some specific files for people to hopefully be able to test out in advance (as those Win7 dialog issues are really annoying me now that I cannot replicate despite most on Win7 seeing them).
And I hope that everyone had a good new year and that their return to work, etc has been without too much pain
-dro
I've finished updated the forum software to the latest version (2.0.13). There shouldn't have been any issues with this (the update went cleanly) but am mentioning it just incase.
I've missed some of the replies / PMs that have been sent over the last few days as the notification emails haven't always been being sent out. I'll look into it fully in the morning though post update and from a quick re-check it seems to be ok again
So apologies over my slowness in reply to some (not helped with unrelated things that have been taking up my time over the last few days).Also after the mess that was the festive period and computer and real life stuff that's been going on over the last 3 weeks or so, today (Tues 10th) I can now get back on with resuming full WACUP development work (as well as getting the missed blog posts, etc finished off and posted) so things are still alive and most things should be sorted over the next day or two.
The next beta build, I think it's going to be some point next week (w/c 16th and not this week as I'd first hoped) but I'm hoping to provide some specific files for people to hopefully be able to test out in advance (as those Win7 dialog issues are really annoying me now that I cannot replicate despite most on Win7 seeing them).
And I hope that everyone had a good new year and that their return to work, etc has been without too much pain
-dro
25
Archive / How Time Flies...
« on: December 12, 2016, 06:21:11 PM »
3 years ago today I helped release Winamp 5.666 build 3516 - a release I'm still proud off!
Winamp it really whips the llama's ass (>.<)
Winamp it really whips the llama's ass (>.<)
26
Archive / Current Forum Display Issues
« on: November 12, 2016, 02:55:56 AM »
Not that it's been commented on (unless I've missed it somehowbut I am aware that some of the action buttons on the forum (mainly when accessed via a mobile / small screen) are just showing as orange buttons with no image.
I'm looking into what is causing the theme to not show the images that it's meant to be so should have it resolved as soon as possible.
If you find anything else then please do say and I'ill do what I can to get it fixed.
-dro
p.s. I've also tweaked some of the mobile view sizes so once the browser cache gets updated then they should appear (e.g. the user info block on mobile is now like the desktop / large screen view so it's side-by-side instead of vertical which gets a fair bit of screen space back so the news banner should appear on mobile viewing now).
I'm looking into what is causing the theme to not show the images that it's meant to be so should have it resolved as soon as possible.
If you find anything else then please do say and I'ill do what I can to get it fixed.
-dro
p.s. I've also tweaked some of the mobile view sizes so once the browser cache gets updated then they should appear (e.g. the user info block on mobile is now like the desktop / large screen view so it's side-by-side instead of vertical which gets a fair bit of screen space back so the news banner should appear on mobile viewing now).
27
General Discussion / Welcome (Please Read First)
« on: October 24, 2016, 12:51:42 AM »Welcome to the Winamp Community Update Pack (WACUP) forums
If you don't already know what WACUP is then please first have a look at https://getwacup.com/ to find out more about it it is and what it intends to achieve.The aim of this forum is to provide a place to talk about and provide support for WACUP from the initial closed beta testing to public releases and whatever else comes from that. You're also welcome to talk about anything Winamp related to associated technology or anything else of interest (nothing dodgy please
). Things will change over the next few months whilst everything gets properly setup so if there are issues with the forum, etc then please do report it so it can be fixed).For those genuinely wanting to participate in the beta testing of WACUP, please drop me a message so you can be added to the beta testing group. For those not wanting to test beta releases and instead just want to wait for non-beta releases then you're also more than welcome to hang around and participate in the general conversations going on
Final thing, if you are having issues logging in / registering on these forums, you can also contact me via the options at https://getwacup.com/#contact so I can help you out.
-dro
Pages: 1 [2]