[PD] seperate GUI communication protocol?

[Jelle Herold]

Hey Thomas and list,

Quoting Thomas Grill (gr at grrrr.org):
> > > if you think of writing a patch editor, it's more complicated ...
> > > but it would also be possible using a pyext object (that's
> > > providing the gui) and a dyn~ object (providing the patching
> > > environment)...
> >
> > yes, that's what I'm looking for. thanks, will look into this.
> >
> > ps. there's an interesting file on the dyn website, "dyn_py - Python
> > module for py/pyext". no documentation however...
> 
> true, but it's just an experimental project in an early stage of
> development and there are presentation slides and Python scripts
> serving as some kind of documentation.
>
> The problem is the whole thing is built on top of PD and doesn't
> integrate - therefore it's not efficient at all.
>
> i have stopped this project for now - most of the functionality is
> integrated into dyn~ anyway.

Out of curiousity I just had a look at this document:
http://puredata.info/community/projects/convention04/lectures/tk-grill/

This seems to be exactly what I need (with or without Python wrapper).
Why is dyn~ better?

Jelle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20050909/b1f608be/attachment.pgp>