Sweet! :) Ok, awesome. You’re ahead on this. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
> On Oct 6, 2016, at 3:49 AM, [email protected] > <mailto:[email protected]> wrote: >> >> 1) External developers who want to support purr-data (pd-l2ork) can #ifdef >> their guis. >> 2) For those who don't want to learn a new toolkit, and for unmaintained >> libraries, it'll be up to purr-data developers. >> >> Until we have good documentation for integrating pd+nwjs, the first option >> may only work well for people who have a toe in both pools. I think that's >> me for cyclone, and I'll be glad to support purr-data directly in the new >> cyclone library as soon as I have a good chunk of time to do it, and some >> time to work out the kinks with Jonathan. > > > I know I’ve mentioned it before, but I wish there was a middle ground where > > the GUI calls were abstracted enough to make these kinds of version/fork > > specific approaches unnecessary. > > https://git.purrdata.net/jwilkes/purr-data#gui-messaging-specification > <https://git.purrdata.net/jwilkes/purr-data#gui-messaging-specification> > > -Jonathan
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
