<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em sex., 3 de fev. de 2023 às 17:40, Ico Bukvic <<a href="mailto:ico@vt.edu">ico@vt.edu</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Patches could be easily edited using sed and awk.</div></blockquote><div><br></div><div>I'm mostly using for a header. There could be a header abstraction instead and it could be rather easy to using magic programming skills to replace and edit this.</div><div><br></div><div>I could do manually as I'm usually not in my right mind :) I've done worse things... I'd do it as a last resource if it all came down to this. I might even do it because of plugdata, which ported it just for the documentation but it's not officially supporting it... let's see </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto">Hopefully you saved yourself the trouble and merged hammereditor changes from pd-l2ork trunk, as that one already works there.</div><div dir="auto"><br><div dir="auto">Best,<br><br>Ico<br><br>-- <br>Ivica Ico Bukvic, D.M.A.<br>Director, Creativity + Innovation<br>Institute for Creativity, Arts, and Technology<br><br>Virginia Tech<br>Creative Technologies in Music<br>School of Performing Arts – 0141<br>Blacksburg, VA 24061<br>(540) 231-6139<br><a href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a><br><br><a href="http://ci.icat.vt.edu" target="_blank">ci.icat.vt.edu</a><br><a href="http://l2ork.icat.vt.edu" target="_blank">l2ork.icat.vt.edu</a><br><a href="http://ico.bukvic.net" target="_blank">ico.bukvic.net</a></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 3, 2023, 15:20 Albert Graef <<a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Ok, so [comment] is another one for the TODO list, because no one in their right mind would volunteer to manually edit 200+ help patches.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 3, 2023 at 8:03 PM Alexandre Torres Porres <<a href="mailto:porres@gmail.com" rel="noreferrer" target="_blank">porres@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">by the way, the [comment] object, which hasn't been ported, could still be left of with no real damage, since it always missed in l2ork/purr data. The thing is that I use it a lot in the documentation of Cyclone. I wouldn't mind removing it though from all help files (but [comment] itself of course). I just don't have the patience to do it.<div><br></div><div>I would gladly accept a PR that removes all [comment] objects from all help files and these could be replaced by regular labels in [cnv] objects. If anyone want to do that for us, should be simple and easy to do, it just requires manual labor and doing a repetitive task for over 200 help files :) </div><div><br></div><div>If that is done, I don't think that merging the new Cyclone will be that complicated. It will probably still miss other features that haven't been ported yet and that's fine too as they were already missing. The biggest issue seems to rely on porting [comment] from scratch just because help files would be kinda ruined.</div><div><br></div><div>cheers</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em sex., 3 de fev. de 2023 às 15:21, Alexandre Torres Porres <<a href="mailto:porres@gmail.com" rel="noreferrer" target="_blank">porres@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Em sex., 3 de fev. de 2023 às 14:56, Albert Graef <<a href="mailto:aggraef@gmail.com" rel="noreferrer" target="_blank">aggraef@gmail.com</a>> escreveu:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Also, as Alexandre mentioned, it makes sense for his cyclone and ELSE to stabilize a bit before we attempt to port them over.</div></div></blockquote><div><br></div><div>Cyclone should be stable, specially now with the last release I plan to do this month</div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Then there's the issue of backward compatibility with legacy cyclone applications that needs some thought. Right now, people can still run many of their old patches that they used to run with classic pd-l2ork or pd-extended with Purr Data, and we'd like to keep it that way. I'm not sure how compatible the latest cyclone still is with older versions. Alexandre, you should know, maybe you can shed some light on this?<br></div></div></blockquote><div><br></div><div>Cyclone is supposed to be backwards compatible, but there are minor exceptions and issues specific to pd-l2ork/purr data, like the [coll] object, which has a 2nd argument in pd-l2ork/purr data for the threaded mode. The thing is that way back, still in MAX 4.0, a 2nd argument was added to [coll] (and this was after Cyclone was developed). We included this behaviour for proper and exact compatibility to MAX. So we created an extra "@threaded" mode for [coll] and this was back in Cyclone 0.3 and this matter was discussed at the time and mentioned to Ivica, I remember. This seems to be the most complicated matter.</div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div></div><div>Maybe some of the tasks involved could be tackled in a future GSoC</div></div></div></blockquote><div><br></div><div>That would be great and I could get involved in that as some "mentor", and also learn better from it how to adapt the GUI externals to nw.js and also how to properly code GUIs in tcl/tk.</div><div><br></div><div>cheers</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div> but I wouldn't hold my breath for it. I'm tempted to look into it at some point, though. I've also been tossing around the idea to add another plugdata-like type of "light" build which would include cyclone and ELSE to mirror what's available in plugdata. That would be useful for those who might prefer Purr for development, but would also like to be able to run their patches as plugins via plugdata. I consider myself in that camp.<br></div><div><br></div><div>Lots of tasks for the infinite TODO list (TM). ;-)<br></div><div><br></div><div>Albert</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 3, 2023 at 3:05 PM Linux ROUEN Normandie <<a href="mailto:linux.rouen@free.fr" rel="noreferrer" target="_blank">linux.rouen@free.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Hello Jonathan and Albert,<br>
<br>
Is there any chance to have sooner or later available under Purr
Data (today with Pd-0.48.0 engine) the following 2 libraries ?<br>
- <a href="https://github.com/porres/pd-else" rel="noreferrer" target="_blank">Else</a> >= v.1.0
(this version needs Pd Vanilla >= v.0.53-1)<br>
- <a href="https://github.com/porres/pd-cyclone" rel="noreferrer" target="_blank">Cyclone</a> (~ Max
7.3.5) >= v.0.6.1 (this version needs Pd Vanilla >= v.0.52-1)<br>
Today Cyclone (~ Max 4) in Purr Data is in a prehistorical version ~
0.1 for years.<br>
<br>
Or at least the following 3 objects ?<br>
- [else/keyboard] - this is a must to have for MIDI applications<br>
- [else/sfont~] - a nice alternative to [fluid~]<br>
- [else/midi] - an alternative to [cyclone/seq]<br>
<br>
Thank you.<br>
<div>- - - - - - - - - - - - -<br>
Best,<br>
Joseph Gastelais<br>
- - - - - - - - - - - - -<br>
</div>
</div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" rel="noreferrer" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email: <a href="mailto:aggraef@gmail.com" rel="noreferrer" target="_blank">aggraef@gmail.com</a>, web: <a href="https://agraef.github.io/" rel="noreferrer" target="_blank">https://agraef.github.io/</a></div></div></div></div></div></div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" rel="noreferrer" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote></div></div>
</blockquote></div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" rel="noreferrer" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email: <a href="mailto:aggraef@gmail.com" rel="noreferrer" target="_blank">aggraef@gmail.com</a>, web: <a href="https://agraef.github.io/" rel="noreferrer" target="_blank">https://agraef.github.io/</a></div></div></div></div></div></div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" rel="noreferrer" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote></div>
_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/listinfo/l2ork-dev</a><br>
</blockquote></div></div>