<div dir="ltr">... And for C) I suggest we call the monster Phreak ;)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/25 Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>The problems you are going to face are:<br></div>1) you need a good package delimitation, with clear contracts (on which package/API do I depend?) both in the Squeak image (to save the package that you want to see reloaded) and in Pharo<br>
</div>2) the package delimitation has to be in good agreement, because the MC tools do not deal with package refactoring<br></div>3) since API are not in agreement, you gonna need plenty of glue for working around changes like trimBoth, includesSubstring: etc...<br>
<br></div>What are your goals exactly?<br><br>A) you want to build on top of smaller kernel?<br>Then once you have 1), why should you go into Pharo rather than building on top of your Squeak kernel?<br><br></div><div>B) you want to profit by clean-ups and refactorings and shiny new architecture made in Pharo?<br>
</div><div>Then yes, porting some interesting Squeak bits to Pharo has some value.<br>But that means you spend a lot of efforts for maintaining those bits alive.<br></div></div>That means switching from old file system to new one, switching from old text system to (yet future) new one, switching to Spec, switching to Settings, Announcements etc...<br>
<br></div><div>C) You have no specific goals, just want to follow the momentum, but keep your confortable Squeak slippers?<br></div>If you end up with hacks for loading all the old Squeak mud, then you'll end up with Squeak, just a different Squeak, and unless you enjoy jumping many hurdles, I don't see the point.<br>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/25 Edgar De Cleene <span dir="ltr"><<a href="mailto:edgardec2005@gmail.com" target="_blank">edgardec2005@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div><br></div><div><br></div><span><div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">De: </span> Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>><br><span style="font-weight:bold">Responder a: </span> The general-purpose Squeak developers list <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.squeakfoundation.org</a>><br>
<span style="font-weight:bold">Fecha: </span> Fri, 25 Oct 2013 14:06:43 +0200<br><span style="font-weight:bold">Para: </span> The general-purpose Squeak developers list <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.squeakfoundation.org</a>><br>
<span style="font-weight:bold">Asunto: </span> Re: [squeak-dev] SqueakTrunk image on <a href="http://build.squeak.org" target="_blank">build.squeak.org</a> broken?<br></div><div><div><br></div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Calibri;word-spacing:0px">
Yes, Pharo is doing a great work of simplification.<br></div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;display:inline!important;font-weight:normal;float:none;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Calibri;word-spacing:0px">On the other hand, it deliberately has zero requirements to make removed parts reloadable, so the task is a bit easier...</span></div>
</span><div><br></div><div><br></div><div>Still exploring and understanding his system, but reporting ReferenceStream to Pharo 2.0 and having DependencyBrowser of Squeak working on it, a long time work could be put our view of Morphic on top of his kernel.</div>
<div><br></div><div>Or Cuis Morph hierarchy.</div><span><font color="#888888"><div><br></div><div>Edgar</div></font></span></div>
<br><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>