<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div><div><blockquote type="cite" class=""><div class="">On Jan 8, 2016, at 9:29 AM, Daniel Iglesia <<a href="mailto:daniel.iglesia@gmail.com" class="">daniel.iglesia@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">I'm glad you asked! It's done in a slightly convoluted, potentially fragile, possibly un-scalable way.</div><div class=""><br class=""></div><div class="">When a user loads a .pd file, pre-proccessing is done on the .pd text to generate _two_ new .pd files, one for execution, and one for display The two communicate with each other. </div></div></div></blockquote><div><br class=""></div>I thought it might be done that way. Does sound knife-edge :) I think it’s not too conceptually difficult to work with send-receives, plus it makes it easier to stream data from the device int Pd on your laptop while developing. <br class=""><br class="">We could work out a way to make the PdParty objects more extensible so you could use the iem implementations as well. This can be included with separating the PdParty UI from the Core and pd gui implementations. SO Submodule instead of copy/paste classes (I could use any bug finding help as well!)<br class=""><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">Separate questions for everyone: </div><div class="">1) you may notice that the current version does not render connection lines. While the patch text lists all the connections (and inlet/outlet indices for them), the app doesn't know how many inlets/outlets each object has. I haven't delved too deeply for it yet, but is there an interface somewhere that will return that information? e.g. here's an atom line for an object and its parameters, tell me how many inlets/outlets. If so, then connection lines could be rendered correctly. (Without it, I could still render conneciton lines, but if there are empty inlets/outlets after a connection then they would not be shown.)</div></div></div></blockquote><div><br class=""></div><div>I stayed away from connection lines mainly because trying to implement “editing” is perhaps an unreasonable task for a single, unpaid developer. Drawing the lines brings that expectation, no? ALso, since I’m using sends/receievs there are no lines to render anyway ...</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">2) Is showing the full set of patch objects (and, eventually, connection lines) even desirable? (Rather than just rendering the gui objects). I'm thinking of an option that would switch their display on/off. (But leave GUI objects, including message boxes)</div></div></div></blockquote><div><br class=""></div><div>Mmm that implies, as I’ve written above, that people can “edit” in MobMuPlat.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">Thanks for input, Dan I.</div><div class=""><br class=""></div></div><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 7, 2016 at 10:55 PM, Dan Wilcox <span dir="ltr" class=""><<a href="mailto:danomatika@gmail.com" target="_blank" class="">danomatika@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">How are you doing this?<div class=""><br class=""><div class="">
<div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;" class="">--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" target="_blank" class="">@danomatika</a><br class=""><a href="http://danomatika.com/" target="_blank" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com/" target="_blank" class="">robotcowboy.com</a></div></div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jan 7, 2016, at 9:19 AM, <a href="mailto:pd-list-request@lists.iem.at" target="_blank" class="">pd-list-request@lists.iem.at</a> wrote:</div><br class=""><div class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);float:none;display:inline!important" class="">- Unlike PdParty/PdDroidParty, you don't need to define send/receive values for every GUI object. Just drop in your PureData patch, with normal object connections, and it should work. (send/receive communication should also still work as well).</span></div></blockquote></div></div></div></blockquote></div></div>
</div></blockquote><br class=""></div><div>--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" class="">@danomatika</a><br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div></div><br class=""></body></html>