Hi folks. I think we need to improve the changes/changelog between Pharo versions: 1.0, 1.1 etc. In addition, we need to document somewhere, how external packages maitainers should update their code. Sometimes, with a deprecated it is easy as you can say which other message to use instead. However, removing TheWorldMenu, FillInTheBlank, Preferences, etc� it is more complicated as you cannot deprecated.� So...if we want maintainers of external packages to update their versions to work with Pharo 1.1 we should document and explain what to do for these situations. For example, I have NO IDEA what to do with code that has references to those classes. Seriously, I don&#39;t have idea how to fix them. <br>
<br>I propose something like Seaside at least: � <a href="http://www.seaside.st/documentation/migration/28to30">http://www.seaside.st/documentation/migration/28to30</a><br><br>Maybe the best start point is:� <a href="http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotOne">http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotOne</a><br>
<br>Sorry I cannot help by myself with this. I am just speaking in case someone can know and can spent few hours and help with this.<br><br>Cheers<br><br>Mariano<br>