adrianfreed
commented
6 years ago Some of those things may break gnu license terms.
Closed equilet closed 6 years ago
adrianfreed
commented
6 years ago Some of those things may break gnu license terms.
equilet
commented
6 years ago Yes, we are on this question with an evaluation. Please see other thread for that.
equilet
commented
6 years ago 
maccallum
commented
6 years ago I don’t think you can remove interleave, unfortunately. zl lace only does two lists, and I don’t know if relying on mxj is a great idea. I just upgraded to the latest OS and had a ton of Java problems.
On Jan 6, 2018, at 3:24 PM, Jeffrey Lubow notifications@github.com wrote:
We've consistently come across issues with a number of objects in the externals release. Let's build a list of the minimum number of things we're willing to support, evaluating things we people (we know of) rely on, and pair down to our core object set.
My understanding of the most current list is as follows below... I don't believe we need to support things like interleave if we provide both example code to do it elsewhere, and to push it into the deprecated folder in order to provide minimal support.
2threshattack~.mxo OSC-route.mxo OSC-schedule.mxo OSC-timetag.mxo OpenSoundControl.mxo SDIF-buffer.mxo SDIF-fileinfo.mxo SDIF-info.mxo SDIF-listpoke.mxo SDIF-ranges.mxo SDIF-tuples.mxo accumulate~.mxo analyzer~.mxo bdist.mxo bench.mxo bench~.mxo bessel.mxo bpf.mxo cambio~.mxo cnmatrix~.mxo decaying-sinusoids~.mxo deinterleave.mxo firbank~.mxo gridpanel.mxo harmonics~.mxo interleave.mxo lcm.mxo list-accum.mxo list-interpolate.mxo migrator.mxo oscillators~.mxo peqbank~.mxo poly.bus~.mxo poly.send~.mxo printit.mxo randdist.mxo rbfi.mxo res-transform.mxo resdisplay.mxo resonators~.mxo roughness.mxo sinusoids~.mxo slipOSC.mxo sphY.mxo thread.fork.mxo thread.join.mxo threefates.mxo trampoline.mxo trend-report.mxo vsnapshot~.mxo waveguide~.mxo whichthread.mxo xydisplay.mxo — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CNMAT/CNMAT-Externs/issues/91, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjjdTtdpBM7brNp1bZzZhH8i_v1RPduks5tIACegaJpZM4RVecM.
equilet
commented
6 years ago Thank you - we'll keep interleave in the main release for now. I was considering moving it to deprecated, but it still seems generally useful.
ramagottfried
commented
6 years ago re: interleave -- sounds good, so... maybe we should remove the "don't use this object!" message in the help file? : )
re: mxj -- I also did a Java install on Windows the other day which was not as fun as I expected it would be.
We've consistently come across issues with a number of objects in the externals release. Let's build a list of the minimum number of things we're willing to support, evaluating things we people (we know of) rely on, and pair down to our core object set.
My understanding of the most current list is as follows below... I don't believe we need to support things like interleave if we provide both example code to do it elsewhere, and to push it into the deprecated folder in order to provide minimal support.