<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><br>
> Because there has been no concrete vision/requirement for a Morphic-based<br>
> emergency evaluator (EE). EE is a relatively rare occurrence (one would<br>
> hope!) and for developers only. But developers typically use _development<br>
> images_ which tend to be fat, not "Stripped", and so might probably include<br>
> ST80 anyway..? The cases seem pretty uncertain and so that's why I'm<br>
> questioning engineering new stuff like this into the image.<br>
<br>
</div></div>This is a bug. It needs to be fixed. It's not new functionality,<br>
unless by "new" you mean "it actually works in Morphic".<br></blockquote><div><br></div><div>By new I meant, "it works when ST80 is unloaded."</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im"><br>
> Particularly we're at a time when I want to get 4.5 out the door, so that<br>
> may be contributing to my aversion to new engineerings. I ask you to at<br>
> least consider simple stub error-handling in situations where<br>
> packages/functionality would be unfulfilled. We can fill in implementations<br>
> later, if needed, but at least you'll have made the structure.<br>
<br>
</div>So you'll be happy with<br>
<br>
* move the current EE to ST-80,<br>
* fix the EE for Morphic (at some point),<br>
* add an AppRegistry for the EE (which is just a hook like ToolSet and<br>
friends, so we don't tangle the two UI frameworks we have so carefully<br>
untangled)<br>
<br>
? If there's a simpler solution, I'm all ears.<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div><br></div><div>I too swamped to dig in today and know. If its small and no potential issue for 4.5, I probably won't complain anymore. But, in general, I do hope extreme TSTTCPW will be considered for cases during the detangling process. We have a dynamic programming system. We wax about developing in the debugger. It's ok to leave some things simply stubbed if there's a chance they may never be encountered.</div>
<div><br></div></div></div></div>