[squeak-dev] The Trunk: Collections-dtl.548.mcz

Chris Muller asqueaker at gmail.com
Fri Dec 13 19:26:19 UTC 2013


>
>
> > Because there has been no concrete vision/requirement for a Morphic-based
> > emergency evaluator (EE).  EE is a relatively rare occurrence (one would
> > hope!) and for developers only.  But developers typically use
> _development
> > images_ which tend to be fat, not "Stripped", and so might probably
> include
> > ST80 anyway..?  The cases seem pretty uncertain and so that's why I'm
> > questioning engineering new stuff like this into the image.
>
> This is a bug. It needs to be fixed. It's not new functionality,
> unless by "new" you mean "it actually works in Morphic".
>

By new I meant, "it works when ST80 is unloaded."


> > Particularly we're at a time when I want to get 4.5 out the door, so that
> > may be contributing to my aversion to new engineerings.  I ask you to at
> > least consider simple stub error-handling in situations where
> > packages/functionality would be unfulfilled.  We can fill in
> implementations
> > later, if needed, but at least you'll have made the structure.
>
> So you'll be happy with
>
> * move the current EE to ST-80,
> * fix the EE for Morphic (at some point),
> * add an AppRegistry for the EE (which is just a hook like ToolSet and
> friends, so we don't tangle the two UI frameworks we have so carefully
> untangled)
>
> ? If there's a simpler solution, I'm all ears.
>
>
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131213/a35b6601/attachment.htm


More information about the Squeak-dev mailing list