- set installation path (suggesting Pd's default search paths, and
offering to create those that are missing)
I wouldn't know if, officially, there are such things as "Pd's default search paths". But then it's clear you mean "standard paths", instead of "default search paths", right? Then again, this raises a few issues. Cause, well, under a recent discussion, it was considered that only the "extra" folder was supposed to be the standard folder, so there are not supposed to be other "standard paths". In other words, it ain't plural, just a singular standard path option, and one that comes always with Pd and doesn't need to be created.
So yeah, what had the need to be created was one folder l
ike that weird and hidden mac folder (~/Library/Pd)... but access to it would still be difficult (as it is invisible). Hence, we have a new folder now (~/Documents/Pd) but that is not a "standard path", just a "regular" path. And I see now "deken" is offering me to create such folders like ~/Library/Pd, after a long discussion that led to the idea we shouldn't use them no more. See this: https://github.com/pure-data/pure-data/pull/139
I know I keep bringing this up here and there, but I think it's a very important detail that can cause many confusions and there is still a lot of inconclusiveness out there, and we're not doing much about it and letting the confusion grow. Now, I was also one of the people who was requesting such a feature several times in Deken, it's all I ever wanted, but the game has really changed because of such recent discussions.
So now we can finally easily create this folder, but it is still invisible and inaccessible to newbies, so not much advantage there. Cause if you need to know how to navigate to that folder, you also know how to create it. So this partially fixes the issue. What was needed there was create it and easily navigate to it, but instead, it was just easier to go to a new folder instead, like ~/Documents/Pd - as we did!
So we have this new standard now that was designed exactly to fix this issue. So this new feature is pointless now, as a new solution (using ~/Documents/Pd) was made, so it is trying to fix an issue (but not in fully fixing it) that has already been fixed and has been in use since 0.48-0! But more importantly, this extra folder has been explicitly declared as a non intentional extra "standard path". See how much confusion this promotes?
And leaving "~/Library/Pd" aside, the other extra standard path option here on the mac: "/Library/Pd" doesn't even get created with the new deken plugin, I figure because it may require admin powers, so it doesn't really help either.
Now, I don't know how the plugin works, but I may assume it gets these paths from Pd, so maybe if my Pull Request gets accepted, no change needs to be made in the Deken plugin and it'll just stop showing them...
Anyway, what I see from this update with this issue is that we have added more unnecessary complexity. Things were cleaner and simpler before. But well, I don't consider this a "deken" issue, but a deeper Pd issue that is popping up in deken and other different places.
That is to say that I'm really happy with the new improvements in deken, congratulations, it is quite exciting!
cheers