<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 3:47 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"> </div></div>It does for SUnit what older commits did for MVC and Morphic: moves<br>
the UI-framework-specific code to that particular UI framework, so<br>
that the core of ToolBuilder remains UI agnostic.<br>
<br>
The problem with shrinking that you refer to is, presumable, that<br>
SUnitToolBuilderTests superclass == AnObsoleteToolBuilderTests? I'd<br>
noticed that, and asked on the list how I might fix that. If you can<br>
suggest an action I can take to remedy the problem, I'm all ears.<br></blockquote><div><br></div><div>No, the problem with shrinking is that I want to remove SUnitToolBuilder without removing TestRunner.</div><div><br>
</div><div>TestRunner provides a GUI for running tests. SUnitToolBuilder provides infrastructure for testing a GUI. They *sound* similar, but really they're completely different, and should be in separate packages. </div>
<div><br></div><div>On the other hand, the ToolBuilder packages were already separate from each other. Admittedly, if you don't have MVC in the image, you probably don't want ToolBuilder-MVC either, but that's not a reason to tie them together; it's reasonable to want MVC only and not use ToolBuilder at all. It seems that these changes have introduced coupling to what was already a nicely modularized group of packages.</div>
<div><br></div><div>I'm sorry I didn't notice this when you first brought it up—I was busy with dirty-world stuff in May and not paying much attention to the Internet. I think the right thing to do is just revert these changes. </div>
<div><br></div><div>Colin</div></div></div></div>