[PD] seperate GUI communication protocol?
gr at grrrr.org
Fri Sep 9 19:05:36 CEST 2005
>Out of curiousity I just had a look at this document:
>This seems to be exactly what I need (with or without Python wrapper).
>Why is dyn~ better?
It's not that dyn~ is better, it's just different - it provides an easy
way for in-patcher scripting, but for that it internally uses the
current m_pd.h API.
The dyn API is far more general, it is a proposal for a C interface to
replace this current PD API, but at the moment it's not integrated into
the PD kernel, therefore needing much more resources than necessary.
This is ok for smaller applications but not for larger ones, as a
replacement for a patcher system would be.
However, you are welcome to use it and i'm happy about any feedback.
More information about the Pd-list