Le 27/07/2017 à 22:17, Fede Camara Halac a écrit :
I agree this is indeed very useful. I would even dare to raise the stakes, if
you allow:
Maybe since there is deken, which adds externals to pd, it would be nice to have a
similar tool that packs and exports a "distribution" of pd for performance,
with all required libs/abs/prefs the patch requires. (Perhaps even for multiple
platforms, but this is asking too much). In mac it would be close to a sort of make app
adapted to the patch.
pd is already multiplatform, I think this would work if it is possible
to add a binary extension to PureData that would use functions in pd
headers for managing the distribution.
Could this be possible? I'd be interested in contributing to this if so and i
still need a huge lot to learn
I've seen pd distributions in many highly experienced users, and so I also ask if this is
the only solution (packing a distribution) when it comes to the "last steps"
before publishing a patch/piece that has a lot of extra stuff that might break if not
mantained/adapted, etc.
Cheers,
fd
fdch.github.io/tv
On Jul 27, 2017, at 2:40 PM, jlistshit <jlists...@kliklak.net> wrote:
Thank you Miller,
that’s at least a better way than going through all by hand and try to list
what one finds… that process usually results in missing things here.
Should i file a feature request?
+1
I think everyone would be happy to see this, and it would make PD more
accessible for non-programmers, too.
Thank you for all you do.
jayrope
- - -
www.jayrope.com
www.aircushionfinish.com
www.ello.co/jayrope
On Jul 27, 2017, at 19:33, Miller Puckette <m...@ucsd.edu> wrote:
This is always a pain, sorry - I often want to do this too. I do it this
way: set "verbose" flag, load the patch, copy all the messages into a
file, then "grep succeeded <file>", then sort. The linux/Mac sort
program has a "-u" flag (unique) that suppresses repeats.
But Pd ought to offer a simpler way to do this :)
cheers
Miller
On Thu, Jul 27, 2017 at 07:13:57PM +0200, jlistshit wrote:
I have a simple question, is there an easy way to list used abstractions of a
patch?
I oftenly pass on patches to fellow musicians and finding used abstractions per
patch can be sticky business - i’d like to not send all abstractions i ever
made instead :)
Thanx for any hints!
jayrope
- - -
www.jayrope.com
www.aircushionfinish.com
www.ello.co/jayrope
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
