I would love to see these implemented, as well, in vanilla cyclone library, with one caveat: wherever possible, I would suggest using an abstraction. Doing so promotes learning and exposes brilliant efficiency of the pure-data core. For instance, one thing that pd-l2ork already does is it provides [prepend] as an abstraction that also annoyingly spits out a warning in the console that the object is deprecated in favor of [list prepend]. While I am sure not everyone agrees with the nagging aspect of the object, this way, users are nudged in the right direction, have an opportunity to dissect the abstraction, while also retaining cross-compatibility. Sure, this may be less efficient than a native object, but likely not by much. Just a thought...On Thu, Feb 11, 2016 at 9:43 PM, Alexandre Torres Porres <porres@gmail.com> wrote:_______________________________________________Howdy, here's a list of relevant new objects to include as externals in Pd. some of them are here because they are just easy and because I was able to do as abstractions or even make an external code draft. Some aren't that simple but I've made into abstractions as well.Anyway, this is what I find important and suggest to have as externals in Pd as we're still missing useful features from themsee attachment and the google docs hereSince I can't code, and since I realize that maintaining the existing library is enough work for now for Fred Jan, we'd need help from enthusiastic coders out there, so I'm trying to recrute friends for the task.cheers
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list