well, since this debate popped out, I can point to a deken issue on github here: https://github.com/pure-data/deken/issues/156 - I had opened it a few days ago, where I suggested a simple change that'd improve some of these issues.

All I ask is that deken consistently suggests "user specific" standard path at first, for all operating systems. As it already does, if the folder doesn't exist, it can create it for you. So then newbies don't need to learn "hacks" to make deken download to a reasonable option out of the box, and it'd all work.

I get this might be too late in the game for the next release round the corner, and I'm cool with that. Also, I've shown that IOhannes has big and awesome plans for deken not in the far future... but anyway, I threw it on the table ;)

cheers

2017-07-29 20:39 GMT-03:00 Alexandre Torres Porres <porres@gmail.com>:

2017-07-29 18:42 GMT-03:00 Roman Haefeli <reduzent@gmail.com>:

Yeah. But why is unhiding necessary in the first place? From what I
understand, Deken suggests the first writable search path it finds, so
the user usually doesn't need to do anything at all but let Deken
download the external to the right place.

Sorry, again on it... "the right place" as of now, is different for each OS, so we don't really have a "Default" considered to be "the right/best place" for most cases.

Moreover, besides the reasoning I gave that a visible folder is needed. For now, on Mac OS, if I want deken to download to the "user specific" folder, I need to do to this hidden secretive place and create the folder in the first place (no, it won't suggest it and automatically create it for me).

cheers