[PD] avoid "properities"/"open" options in abstractions

Dan Wilcox danomatika at gmail.com
Tue Mar 6 18:41:01 CET 2018


It also goes against one the best things about Pd: peeking under the hood for abstractions. Are adding dependencies/workarounds really worth the time for something that is at most a "nice to have"? (I ask myself this more and more the older I get...)

> On Mar 6, 2018, at 6:31 PM, pd-list-request at lists.iem.at wrote:
> 
>> but if you just want to prevent users from opening up objects in your
>> publicly facing installation
> 
> Nope, the idea is just try and make an abstraction behave like a compiled
> external. I know some people might think that's crazy, ludicrous,
> pointless, stupid, counterproductive, shameful and just bad... but... I
> liked the idea :)

--------
Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20180306/acf5ffda/attachment.html>


More information about the Pd-list mailing list