Re: [PD] list item picker widget - [declare] lib paths
In some recent and proposed updates to declare and the loader, the movement is toward being able to load both compiled and abstraction libraries without having to use both -lib & -path, but we are not there yet: https://github.com/pure-data/pure-data/pull/440 <https://github.com/pure-data/pure-data/pull/440> In many ways, -stdpath and -stdlib is legacy but of course will most likely not be removed or explicitly deprecated unless there is a real need. It is however highly encouraged *not* to use them, ie. no longer having users manage stuff inside the macOS Pd .app bundle. In your case with netpd and bundled resources, then I imagine they are still quite useful. :) > On Feb 16, 2021, at 2:37 PM, pd-list-requ...@lists.iem.at wrote: > > Message: 2 > Date: Tue, 16 Feb 2021 14:37:19 +0100 > From: Roman Haefeli mailto:reduz...@gmail.com>> > To: Pd-List mailto:pd-list@lists.iem.at>> > Subject: Re: [PD] list item picker widget - [declare] lib paths > Message-ID: <mailto:f592ac96dd0de66fa4679b609eb2e7096e9e2864.ca...@gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Thanks for the full picture, Dan. > > I guess the main point is that when Pd users go along the defaults, > they need patches to use -path and -lib. > > Even more, -lib and -path _also_ work for stuff installed in any of the > standard search paths like /extra. Assuming that people use a > recent version of Pd, there can be no harm in using -lib and -path. > They cover more use cases. Thus, I'd say using -lib and -path should be > considered the canonical way of loading libraries. > > Roman Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] list item picker widget - [declare] lib paths
Thanks for the full picture, Dan. I guess the main point is that when Pd users go along the defaults, they need patches to use -path and -lib. Even more, -lib and -path _also_ work for stuff installed in any of the standard search paths like /extra. Assuming that people use a recent version of Pd, there can be no harm in using -lib and -path. They cover more use cases. Thus, I'd say using -lib and -path should be considered the canonical way of loading libraries. Roman On Tue, 2021-02-16 at 14:09 +0100, Dan Wilcox wrote: > I don't know if this is purely "canonical", but this is how it works: > > The Document's path was added to provide a default location for deken > to download externals, ~/Documents/Pd. It is purely optional but > builds on the existing search path functionality. The idea is help > beginners manage search paths and move away from installing stuff to > extra or ~/pd-externals, etc. It is implemented as a gui plugin which > is included with Pd. The source is in the Pd tcl folder. > > If the Documents path is used, an "externals" subfolder is created > and added to the search paths, so installing something via deken, > should only require [declare] -path and/or -lib for usage. Basically, > if an abstraction-only library is in ~/Documents/Pd/externals ala > ~/Documents/Pd/externals/extname, then it should be found with > [declare -path extname] assuming the user is using the Documents path > *and* has installed the "extname" external to the default location > via deken. You can, of course, manually add external folders as well. > > Additionally, you can restrict declare to only look in relative paths > when adding folders relative to a patch by prepending . or .. to the > beginning, ie [declare -path ./extname] will only look for a folder > named "extname" in the same folder as the patch, without looking in > any of the user or "standard" search paths. > > > On Feb 16, 2021, at 12:00 PM, pd-list-requ...@lists.iem.at wrote: > > > > Message: 2 > > Date: Tue, 16 Feb 2021 10:33:52 +0100 > > From: João Pais > > To: pd-list@lists.iem.at > > Subject: Re: [PD] list item picker widget - [declare] lib paths > > Message-ID: > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > > > I'm not quite sure what the canonical declaration style is, > > > > -lib/- > > > > path or -stdlib/-stdpath. I guess the former will work better > > > > for > > > > Pd's own default setup. > > > I should say this is true since 0.50 or so. Before that, > > > -stdlib/- > > > stdpath was the common thing to use. > > What would be then the canonical now, no "-std"? I can change that > > easily in my patches, but would be good to have it confirmed. > > > Dan Wilcox > @danomatika > danomatika.com > robotcowboy.com > > > > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list signature.asc Description: This is a digitally signed message part ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] list item picker widget - [declare] lib paths
I don't know if this is purely "canonical", but this is how it works: The Document's path was added to provide a default location for deken to download externals, ~/Documents/Pd. It is purely optional but builds on the existing search path functionality. The idea is help beginners manage search paths and move away from installing stuff to extra or ~/pd-externals, etc. It is implemented as a gui plugin which is included with Pd. The source is in the Pd tcl folder. If the Documents path is used, an "externals" subfolder is created and added to the search paths, so installing something via deken, should only require [declare] -path and/or -lib for usage. Basically, if an abstraction-only library is in ~/Documents/Pd/externals ala ~/Documents/Pd/externals/extname, then it should be found with [declare -path extname] assuming the user is using the Documents path *and* has installed the "extname" external to the default location via deken. You can, of course, manually add external folders as well. Additionally, you can restrict declare to only look in relative paths when adding folders relative to a patch by prepending . or .. to the beginning, ie [declare -path ./extname] will only look for a folder named "extname" in the same folder as the patch, without looking in any of the user or "standard" search paths. > On Feb 16, 2021, at 12:00 PM, pd-list-requ...@lists.iem.at wrote: > > Message: 2 > Date: Tue, 16 Feb 2021 10:33:52 +0100 > From: João Pais mailto:jmmmp...@gmail.com>> > To: pd-list@lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] list item picker widget - [declare] lib paths > Message-ID: <mailto:e362b696-301a-ee0d-e4d9-a5db6ee32...@gmail.com>> > Content-Type: text/plain; charset=utf-8; format=flowed > >>> I'm not quite sure what the canonical declaration style is, -lib/- >>> path or -stdlib/-stdpath. I guess the former will work better for >>> Pd's own default setup. >> I should say this is true since 0.50 or so. Before that, -stdlib/- >> stdpath was the common thing to use. > What would be then the canonical now, no "-std"? I can change that > easily in my patches, but would be good to have it confirmed. Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/> ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] list item picker widget - [declare] lib paths
I'm not quite sure what the canonical declaration style is, -lib/- path or -stdlib/-stdpath. I guess the former will work better for Pd's own default setup. I should say this is true since 0.50 or so. Before that, -stdlib/- stdpath was the common thing to use. What would be then the canonical now, no "-std"? I can change that easily in my patches, but would be good to have it confirmed. ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
