Thanks, Dan. I understand this, and i also have seen this manner of working in other experienced users who send a folder with tons of .pd files (and it often takes a while to figure out which one to open). But, i agree this works and it's very convenient. I also think this needs some pd knowledge on the person receiving the folder, depending on the case. Especially if Its a patch from the extended era

I am aiming at a different thing, though, a patch bundle-izer that creates an executable any person can click and open and a pd is there running with whatever lib/abs your patch needed (in whatever target platform you specify). This is meant to send to unexperienced users. It would be a no-brainer last step before the email attachment. 

Anyway, i know this is wishful thinking so thanks!!


fdch.github.io/tv



On Jul 28, 2017, at 5:10 AM, Dan Wilcox <danomatika@gmail.com> wrote:

You can do that now, just put the libs and abstractions in the same folder as the patches.

Pd looks in the local path of the patch as well as the system & user specified locations, plus you can use [declare] as well:

On Jul 27, 2017, at 10:53 PM, pd-list-request@lists.iem.at wrote:

From: Federico Camara Halac <camarafede@gmail.com>
Subject: Re: [PD] Easy way to list used abstractions in patch?
Date: July 27, 2017 at 10:51:49 PM GMT+2
To: Matt Davey <hard.off@gmail.com>


Well I don't know about how extended worked, since I really never used it. I only mean to 'export' into a pd distrib that is only intended to use with a particular patch that only has the requirements of that patch
 
if you could do that, then you could just autogenerate pd-extended, no?