<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div dir="ltr" id="yui_3_16_0_1_1444833358434_13070"><span id="yui_3_16_0_1_1444833358434_13069">The GUI port I'm working on for Pd-l2ork should </span>essentially replace Pd-extended. But I still have to get it building on OSX.</div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867"><br></div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">There will be some inconveniences:</div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">* I'm not porting Toxy. (But Pd Vanilla broke support for it anyway.)</div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">* Aside from some key GUI externals, I'm only going to port GUI externals </div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">"a la carte". That is, if your patches depend on it and it would be burdensome </div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">to find a workaround, I'll go ahead and (try to) port it.</div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867"><br></div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">But in general, all the other externals that ship with Pd-extended should work </div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">just fine (and do work atm in Pd-l2ork).</div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867"><br></div><div dir="ltr" id="yui_3_16_0_1_1444833358434_12867">-Jonathan</div> <br><div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font size="2" face="Arial"> On Wednesday, October 14, 2015 11:22 AM, "rolfm@dds.nl" <rolfm@dds.nl> wrote:<br> </font> </div> <br><br> <div class="y_msg_container"><br>it looks like the future of pd-extended is going to be 'deken'.<br>what to do then about portability?<br><br>i make patches for people who don't know a lot about programming.<br>plus they are on Mac, i'm on Windows.<br>one time downloading the right version of Pdext is enough;<br>i can give them my patches and they just run them.<br>when i make changes, new features: there's no hassle for them.<br><br>using Vanilla & deken is something else.<br>declaring a library in the patch is not enough.<br>including the library in the patch-package works only on the same type of OS;<br>Windows & Windows, Mac & Mac, (Linux & Linux?).<br><br>one method could be a deken-connected feature to automatically <br>download a declared lib when it's not present.<br>what about updates or changes in a lib in that case?<br><br>the organisation of pd-ext somehow included a kind of gate-keeping, <br>which resulted in a stable Pd-system.<br>i'm still using Pdext 42.5 and the included libs a lot (because of the <br>old machines in my installations). the same libs are functional in <br>Pdext 43.4.<br>so one could argue that there's no great need for a portability <br>design. just download everything that's necessary (and available) and <br>it will work for quite some time.<br><br>?<br>rolf<br><br><br>_______________________________________________<br><a ymailto="mailto:Pd-list@lists.iem.at" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br><br><br></div> </div> </div> </div></div></body></html>