<br><br><div class="gmail_quote">On Wed, Aug 12, 2009 at 4:16 PM, Gary Dunn <span dir="ltr"><<a href="mailto:osp@aloha.com">osp@aloha.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
What makes a plugable morph plugable? In terms of building apps, what is the significance of being plugable? Do plugable morphs work especially well as a team?</blockquote><div><br></div><div>Pluggable refers to the parameterisation of some MVC or Morphic component's communication to the model so that the selectors it uses to set/get state are parameters and internally the component uses perform: et al to apply the selectors to the model. e.g. look at implementors and senders of #getText: in Monticello and you'll see PluggableTextSpecs (from which PluggableTextMorphPlus instances are built) being created with text accessors such as #verrsionName #logMessage & plain old #text. In olden days one used to use subclasses that would implement state accessors with direct message sends of the relevant selectors. The pluggable style cut down on a proliferation of classes.</div>
<div> </div><div>best</div><div>Eliot</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<font color="#888888"><br>
--<br>
Gary Dunn, Honolulu<br>
<a href="mailto:osp@aloha.com">osp@aloha.com</a><br>
<a href="http://openslate.net/" target="_blank">http://openslate.net/</a><br>
<a href="http://e9erust.blogspot.com/" target="_blank">http://e9erust.blogspot.com/</a><br>
Sent from a Newton 2100 via Mail V<br>
<br>
</font></blockquote></div><br>