[PD] Preferred/best practice for loading external objects
IOhannes m zmoelnig
zmoelnig at iem.at
Tue May 17 10:46:48 CEST 2016
On 2016-05-17 09:59, Lorenzo Sutton wrote:
>> ... in that order. We can consider ~/pd-externals to be obsolete.
> I know the discussion in mostly about externals, but personally I also
> have a bunch of home-made abstractions (and a couple of gui plugins) I
> always like to have in my Pd search path and ~/pd-externals/ is nice
> a) it's "portable" when I back-up my home directory
> b) it's (mostly) independent of Pd versions...
> But, because this is a specific use case for my set-up/machine
0) how does your setup break with the new behavious?
and to answer you r specific questions:
a) ~/.local/lib/pd/extra is in your home directory as well, so how is it
b) i don't see anything version specific in the new behaviour.
i can only see two possible issues:
a) you only backup "visible" folders in your home-directory, so you
would miss ~/.local/lib/pd/extra
b) your olde versions of Pd would not know about ~/.local/lib/pd/extra
and only search in ~/pd-externals; so putting externals into the new
path would be "incompatible" with loading them from old Pd's.
a simple fix for (b) is to keep your externals in ~/.local/... and
symlink ~/.local/lib/pd/extra to ~/pd-externals
a simple for for (a) is to do the reverse (keep your externals in
~/pd-externals and make ~/.local/lib/pd/extra a symlink to this place);
this would also fix (b), but for aesthetic reasons i dislike it a bit
the drawback with this is, that a Pd-version that looks for externals in
both places, will find them multiple times (which will give ugly error
messages on the console).
the easiest fix for this is to just remove ~/pd-externals entirely from
the built-in search paths and add a BIG UPGRADING NOTE that mentions the
symlinks (and/or "adding -path").
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pd-list