<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hello Jonathan,<br>
<div class="moz-signature"><br>
- <a moz-do-not-send="true"
href="http://msp.ucsd.edu/Pd_documentation/x5.htm">Pd
Documentation chapter 5. current status</a><br>
A complete releases list with details per release from Pure Data
v.0.0.1 to latest v.0.51-0.<br>
<br>
- <a moz-do-not-send="true"
href="https://github.com/pure-data/pure-data/blob/master/src/CHANGELOG.txt">pure-data/src/CHANGELOG.txt</a>
- Less complete and stopped at v.0.42, but see also the end of the
list.<br>
<br>
Best,<br>
Joseph Gastelais<br>
<br>
- - - - - - - - - - - - - - - - - - - -<br>
</div>
<div class="moz-cite-prefix">Le 19/06/2020 à 17:29, Jonathan Wilkes
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAOA7yC5ku5Qk5+a5wJTB7mk0ji_LYTecf=NdRhppzBAruysPTA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">On Fri, Jun 19, 2020 at 9:50 AM Matt Barber <a class="moz-txt-link-rfc2396E" href="mailto:brbrofsvl@gmail.com"><brbrofsvl@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Thanks for this, Guillem.
I'm inclined to suggest that we try to import Vanilla's undo routines if they'd be useful for your project. It may prove easier to do that if we also want to grab the triggerize function, since the triggerize undo is pretty involved and seems to depend on the rest of the undo infrastructure.
I'd like to reiterate the main complaint I get from Pd users who want to migrate to Purr but who don't ultimately end up doing so: Purr is behind on features from recent versions of Vanilla and so more recent patches don't work. I think it's worth being proactive in including the new stuff when possible, and this might be a good opportunity to do so.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Does Pd Vanilla have a comprehensive listing of new features for each release?
If so it would be helpful if someone could compile a list that has the
feature list per release.
-Jonathan
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
MB
On Tue, Jun 16, 2020 at 11:54 AM Ivica Bukvic <a class="moz-txt-link-rfc2396E" href="mailto:ico@vt.edu"><ico@vt.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
I propose proceeding with whatever is easiest, most maintainable, and least likely to break things. So, cherry picking fixes will be important.
Best,
Ico
--
Ivica Ico Bukvic, D.M.A.
Director, Creativity + Innovation
Institute for Creativity, Arts, and Technology
Virginia Tech
Creative Technologies in Music
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
<a class="moz-txt-link-abbreviated" href="mailto:ico@vt.edu">ico@vt.edu</a>
<a class="moz-txt-link-abbreviated" href="http://www.icat.vt.edu">www.icat.vt.edu</a>
<a class="moz-txt-link-abbreviated" href="http://www.performingarts.vt.edu">www.performingarts.vt.edu</a>
l2ork.icat.vt.edu
ico.bukvic.net
On Tue, Jun 16, 2020, 11:47 Guillem Bartrina Moreno <a class="moz-txt-link-rfc2396E" href="mailto:guillembartrina@gmail.com"><guillembartrina@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hi,
I have been checking pd vanilla "triggerize" feature, as Matt suggested, together with its undo system. It turns out that pd vanilla already has an atomic multi-step undo system implemented that allows us to start a sequence of undo actions, fill it with all actions that we need and then finalize it. Then, while undoing, if the system encounters the start/end of the sequence it executes all undo steps until the end/start is reached.
As you have been talking about merging some pd vanilla interesting features into purr data, what do you think about this one?
I don't know what would be better. I have checked the implementation differences between vanilla and purr data and there are some of them that could probably break the system if we do a direct merge. Basically pd vanilla changed the place where the undo queue is stored and therefore how it's accessed, and some other implementation differences and add-ons.
An option would be porting only the things that we want to add to purr data, adjusting them as needed. Another one would be implementing them from scratch, as intended.
Best,
--
Guillem Bartrina Moreno
_______________________________________________
L2Ork-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class="moz-txt-link-freetext" href="https://disis.music.vt.edu/listinfo/l2ork-dev">https://disis.music.vt.edu/listinfo/l2ork-dev</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
L2Ork-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class="moz-txt-link-freetext" href="https://disis.music.vt.edu/listinfo/l2ork-dev">https://disis.music.vt.edu/listinfo/l2ork-dev</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
L2Ork-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class="moz-txt-link-freetext" href="https://disis.music.vt.edu/listinfo/l2ork-dev">https://disis.music.vt.edu/listinfo/l2ork-dev</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
L2Ork-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class="moz-txt-link-freetext" href="https://disis.music.vt.edu/listinfo/l2ork-dev">https://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
</blockquote>
<br>
</body>
</html>