[PD] libpd separating gui from core

Hans-Christoph Steiner hans at at.or.at
Mon Feb 17 16:48:51 CET 2014


I think that the way forward with the pd/gui separation is to work on the low hanging fruit, things that are easy to fix.  Let the hard parts for later, which will only be a couple areas.

So that means looking at everywhere where sys_gui() or sys_vgui() is called, and seeing how the raw Tcl in those calls can be converted into Tcl procs.  The syntax for calling Tcl procs is very close to a Pd list, so that is an easy way to get close.

The Pd dev community has always been plagued with a desire for grand plans before starting work.  And that has proven to mean nothing happens.

.hc

On 13/01/2014 15:32, Dan Wilcox wrote:
> As Hans has proposed for years, IMO this is really the only way to
> perhaps solve the "PD gui development doesn't move fast enough" problem
> in the long term. In this case, Miller would have the core (in libpd) &
> the pd-vanilla wrapper gui formally separated while everyone else can
> then use the same libpd core within other flavors. The DSP core is the
> heart and soul and I see no reason to try and change that in any way.




More information about the Pd-list mailing list