<br><br><div class="gmail_quote">On Thu, Feb 2, 2012 at 1:52 AM, Rich E <span dir="ltr"><<a href="mailto:reakinator@gmail.com">reakinator@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I do think it is important to separate these things into bite size chunks (I think IOhannes mentioned this as well during his LAC talk). Peter, your blog post talks of creating an API for editing patches (<a href="http://nettoyeur.noisepages.com/2012/01/refactoring-pure-data/" target="_blank">here</a>), and while I look forward to these capabilities, I think this is also a separate job as to the one Miller proposed on this thread, which I see as taking care of the static state in pd. I don't think I could prioritize these two different jobs, but I'd say multiple instances allows us to definitively crush max, as we'll have a pd vst. :)</blockquote>
<div><br>I harbor no hostility to Max, but I agree that getting rid of global state and allowing multiple instances should be the first order of business. Any ideas?<br>Cheers,<br> Peter<br> <br></div></div>