<div dir="ltr"><div>Yes I still think that it was a mistake to not do the massive SmalltalkImage current -> Smalltalk rewrite.<br></div>I'm pretty sure that Pharo went further than Squeak with this respect!<br></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/22 Casey Ransberger <span dir="ltr"><<a href="mailto:casey.obrien.r@gmail.com" target="_blank">casey.obrien.r@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Okay so from my point of view, SmalltalkImage is an extra class, a fifth wheel.<br>
<br>
In practice, and mainly because Morphic is so different, this is a really easy thing to deal with. Anything with a UI will require significant reimplementation in order to run over Cuis, so this particular case, like the difference in how authors are identified, is a minor nuisance that pops up a lot. When the debugger opens to complain about a missing SmalltalkImage, I just replace it with Smalltalk (IIRC) and that generally works.<br>
<br>
In general though, you're right. Compat packages are the way to go.<br>
<div class="HOEnZb"><div class="h5"><br>
On Jul 21, 2013, at 3:26 PM, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
<br>
> If you badly need to import packages in Cuis, then nothing prevents you to add a Squeak-Compatibility layer (or Pharo), and let Cuis itself clean.<br>
<br>
</div></div></blockquote></div><br></div>