I should add, if you want to make sense of the pd-extended.git, read
the 'patch_series' branch:
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended.git;a=shortlog;h=refs/heads/patch_series
If you are working with it, then work off of the 'master' branch
because 'patch_series gets rebased so that it remains a collection of
patches on top of pure-data.git.
Here's the specific commit:
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended.git;a=blobdiff;f=tcl/pdwindow.tcl;h=bd109606db0bb3fb739253726844986effa5e35d;hp=bb1e1d65a68d574df5cdb341a650f34b88ccb491;hb=b62774fb34e5b5589732b610dbf53d4d6e938dda;hpb=456a3688582b3dbdb610135554f46493f867b5f1
But its not really going to make sense if you are used to reading
0.42.5 code. I think your best bet is to start off of Miller's pure-
data.git and start making the pd-l2ork changes into a series of
commits on top of Miller's pure-data.git. That'll make it really easy
to keep in sync with pure-data.git and pd-extended.git.
.hc
On Oct 21, 2011, at 11:23 PM, Ivica Ico Bukvic wrote:
Hans and all,
There was recently a mention of threaded output in pd-extended 0.43
which prevents the console from overwhelming the main thread. Has
this been implemented and if so, in which file is this
implementation located?
Any help on this one is most appreciated!
Best wishes,
Ico
----------------------------------------------------------------------------
Programs should be written for people to read, and only incidentally
for machines to execute.
- from Structure and Interpretation of Computer Programs
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
