<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 11:13 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:</div>
<div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Undoing these changes, I think I realise why I did it. Morphic depends<br>
on ToolBuilder-Morphic, and I tried to break that dependency by<br>
folding TB-M into Morphic. Once that was done, what's good for one<br>
framework should be good for the others. Only of course while Morphic<br>
shouldn't depend on TB-M, folding TB-M into Morphic means that Morphic<br>
still depends on TB, which it shouldn't. (Because using TB was<br>
supposed to be optional. It's TOOLBuilder, not GenericUIBuilder.<br>
<br>
So Morphic still depends on ToolBuilder-Morphic, because<br>
PluggableSystemWindowWithLabelButton subclasses PluggableSystemWindow,<br>
and because UserDialogBoxMorph uses PluggableButtonMorphPlus.<br></blockquote><div><br></div><div>Ah, that makes sense. </div><div><br></div><div>So we need to figure out how to break that connection. Perhaps we'd get rid of all the Plus morphs and fold that functionality into either Morphic (PluggableFooMorph) or ToolBuilder (extensions to PluggableFooMorph) depending on whether its generally useful. </div>
<div><br></div><div>Colin</div></div></div></div>