Well, it all comes down to style now if we've determined theres no speed diff.<br>Right now I've been building my objects with both traditional inlets/outlets as <br>well as send/recieve mirrors named on the object name, first creation arg ala
<br>Chris McCormick's s-abstractions.<br><br>So [rc-arp arp1] has a midi note inlet as well as a matching [r arp1/notein] receive.<br>It also has receives for each gui element. This is nice in that I can connect<br>things in the traditional manner, but also quickly grab things in other parts of the patch.
<br><br>It relatively easy to keep track of what's going on since the receives are based on the<br>name and functionality, although at this point I find myself using connections much more.<br>Another note is that I have recently upgraded to a newer used computer after I somehow
<br>connected 220VAC to the old laptop's Audio In which means I have a smaller resolution display.<br>There's a big diff in patching practice between 1400x1050 and 1024x768.<br><br>Hmmm I have't tried this "global message bus" idea yet.
<br><br><div class="gmail_quote">On Dec 18, 2007 7:49 PM, Roman Haefeli <<a href="mailto:reduzierer@yahoo.de">reduzierer@yahoo.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, 2007-12-18 at 19:31 -0500, marius schebella wrote:<br>> I think connections are slightly faster, but that is negligible. the<br>> more important aspect is programming style/readability/layout/program
<br>> flow, and in this respect connections are definitely preferable. with<br>> send/receive you end up with spaghetti code.<br>> Maybe when working with a lot of abstractions, it makes sense to use<br>> send/receive, just because drawing too many connections is a pain. but
<br>> most of the time connections make your life easier.<br>> marius.<br><br>maybe when working with a lot of abstractions, it makes sense to use<br></div>methods, that are all sent to the same inlet and inside the abstraction
<br>[route]d apart again. it makes it also easier to debug, because you need<br>to create only one connection to one [print] in order to see, which<br>message is sent in what orde to the abstraction.<br><font color="#888888">
<br>roman<br></font><div class="WgoR0d"><br><br><br>___________________________________________________________<br>Telefonate ohne weitere Kosten vom PC zum PC: <a href="http://messenger.yahoo.de" target="_blank">http://messenger.yahoo.de
</a><br><br></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Wilcox<br>danomatika<br><a href="http://www.robotcowboy.com">www.robotcowboy.com</a>