[PD] libpd separating gui from core

Ivica Ico Bukvic ico at vt.edu
Thu Feb 27 22:00:17 CET 2014


 

For instance, it seems like there are two main concerns floating around: 

 

a) multiple instances of pd

b) separating GUI from core

 

I would add a c) here which is what pd-l2ork has been doing, namely getting
rid of all known bugs and streamlining experience until it reaches a level
of stability where issues are a rare occurrence. My take is that refactoring
becomes a lot easier at that point because one will have a much better idea
what components should look like. Otherwise, fixing things post-refactor
will net in even more headaches where two parts may end-up being potentially
out of sync with each other, resulting in a broken app.

 

There are other suggestions like platform-specific vectorization and
multi-threaded support, but if you try to do these at the same time, you
reduce the chance of ever getting the code back into vanilla.  They can be
taken on after.

 

IMO, the best thing to do going forward for a) would be to sync up with
Miller and what he netted out with last time this was discussed ( see
thread: http://lists.puredata.info/pipermail/pd-dev/2013-12/019702.html). It
seemed like he was proposing to take a hefty chunk of the work on, or maybe
if he is confident in merely the approach, someone else can have a go at it.

 

Having been on this list for quite a few years, I know of only one person
who was allowed to significantly contribute/alter the core and that was
Hans. And even that amounted to mainly cleaning up tk code to make it more
legible (yes, this is a gross oversimplification, there was
internationalization, console verbosity, and many other little things, but
in general the brunt of the work was lateral in nature).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20140227/e494d3e5/attachment.htm>


More information about the Pd-list mailing list