<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The simplest answer: both. It’s up to what you need / how you work. <div class=""><br class=""></div><div class="">RjDj encouraged people to package *all* the libs needed by a scene within the scene itself. This ensures you can pass a scene to someone else and know it has all of it’s dependencies. The downside is that then you end up having *alot* of redundant abstraction lib copies.<div class=""><br class=""></div><div class="">The libs folder is kind of like Desktop pd’s extra folder so you have a central place to put commonly used abstractions. Bundling libs within a scene will still work of course as, like Desktop pd, the local scene copy should override the libs copy. A secondary reason PdParty has the libs folder is to allow users to override/modify the few built-in abstractions as there is a secondary copy kept internally. I may remove having a direct copy already placed in libs in the future.</div><div class=""><br class=""></div><div class="">In any case, one of the important points for me is that, generally, PdParty scenes should work on Desktop. This is partially experience for being able to run a backup set on my laptop if the hardware setup fails :P</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" class="">@danomatika</a><br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Aug 8, 2016, at 10:21 AM, mitchell turner <<a href="mailto:mmturner2468@gmail.com" class="">mmturner2468@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Dan,<br class="">I have finally gotten around to trying out PdParty and absolutely love it. Thanks for all of the work you did getting this to run. I’m sure I’m not the only one who appreciates your work.<br class=""><br class="">I have a question regarding how best to use my own abstractions within PdParty on iOS. I have been successful using my abstractions two ways:<br class="">1) copy my abstraction into the PdParty directory that contains my main patcher. <br class="">2) copy my abstraction into the main “lib” directory inside PdParty. <br class=""><br class="">I guess my question is: what is the best place to put user-created abstractions within the file structure of PdParty.<br class=""><br class="">For those interested, I’m using the latest version of PdParty on iOS 9.3.4 and Pd Vanilla 0.47.0. <br class=""><br class="">Thanks again,<br class="">Mitch<br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></div></div></body></html>