It seems that the main/only thing to do in order to update the Pd-extended core is to update vanilla to incorporate the GUI rewrite stuff, as well as closebang and initbang (what other things?). It seems that someone just needs to go through and copy all of the code directly, deciding which GUI things to keep and which to discard
-Sebastian
On 05/03/15 14:12, Seb Shader via Pd-list wrote:
It seems that the main/only thing to do in order to update the Pd-extended core is to update vanilla to incorporate the GUI rewrite stuff, as well as closebang and initbang (what other things?). It seems that someone just needs to go through and copy all of the code directly, deciding which GUI things to keep and which to discard
isn't that exactly what has already been done in the last few versions of vanilla?
And if you take a different view of the appropriate things to include, of backward compatibility, of the pace of changes, of how desirable a fancier 'modernised' GUI is etc then there has been a lot of that done in pd-l2ork as well.
The other issue lurking in the background with libraries is that copyleft licensing is avoided by vanilla and by those who need to comply with Apple's conditions for their app stores and mainstream access to their platform.
Simon
I believe a lot of the original GUI rewrite has been incorporated into Pd Vanilla. At least the part where pd.tk was broken into separate tcl packages. -Jonathan
On Wednesday, March 4, 2015 10:14 PM, Seb Shader via Pd-list <pd-list@lists.iem.at> wrote:
It seems that the main/only thing to do in order to update the Pd-extended core is to update vanilla to incorporate the GUI rewrite stuff, as well as closebang and initbang (what other things?).It seems that someone just needs to go through and copy all of the code directly, deciding which GUI things to keep and which to discard -Sebastian _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list