I'm all up for discussing how we can change things to achieve a goal.
First we had them all showing and then we chose to hid foreign architectures, right?
Back then, the idea was to highlight the native ones, this still happens when we decide to show them, foreign architecctures are greyed out.
What I also think it's confusing now is that if you decide to show foreign architectures and have that other checbox o by default, you get native options that are greyed out. It's hard to differentiate the native ones from the foreign. It's confusing.
My idea: we create a new standard for highlighting the first option. This can be shown in bold, and perhaps a different color (blue is nice, it's what links usually are colored like).
We change the behaviour of that box, and tell it to hide others that are not the latest (unchecked by default). This is not "treated" as foreign. Which means, if we have it marked and choose to show foreign, only the latest version of the foreign releases are shown.
I guess this makes sense from a design point of view.
cheers
But treating in the same was as foreign architecture (hiding it) doesn't seem clever
If the idea is to highlight the
Em dom., 28 de nov. de 2021 às 12:17, Dan Wilcox danomatika@gmail.com escreveu:
My 2 cents:
From a beginners perspective, limiting to the latest (stable) release makes sense as a long list of various versions and tests with only some number and date in a small font / embedded in the file name to differentiate them could be very confusing. Perhaps there is a good middle ground where the option can be enabled by default but the latest, say 2-3 releases are listed with "stable" and "test" better marked? Or perhaps this is the new default behavior and the checkbox is reversed as in it becomes "Show all versions of a library"?
Don't forget that just because you get used to something, doesn't mean that's the best approach or that's the way it has to stay. I recall a few people on this list making that point about certain aspects of the GUI... :)
On Nov 28, 2021, at 4:05 PM, pd-list-request@lists.iem.at wrote:
Message: 1 Date: Sun, 28 Nov 2021 16:05:50 +0100 From: Christof Ressi info@christofressi.com To: Pd-List pd-list@lists.iem.at Subject: Re: [PD] Pd 0.52 test 2 is out Message-ID: 2ec67a1d-1b01-98d2-d1dd-247d33d93e90@christofressi.com Content-Type: text/plain; charset="utf-8"; Format="flowed"
I think this kind of unwarned change can be really confusing, see my case here :) it's a cool option, but maybe not checked by default?
I also think that the option should be off by default. For example, let's say there is a stable "vstplugin~-0.5.2" package on Deken. Now, if I upload "vstplugin~-0.6-test" Deken would only show that and would hide the stable release...
Or should we rather stop uploading test releases to Deken?
Christof
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com