<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Well, then such compatibility fixes should rather happen in Squeak5.3beta. :-)<div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 05.09.2019 10:49:14 schrieb Tobias Pape <das.linux@gmx.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><br>> On 05.09.2019, at 10:43, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>> <br>> Hi, all.<br>> <br>> Should all be fixed in Trunk now. Load it like this:<br>> <br>> Installer ss<br>> project: 'MetacelloRepository';<br>> addPackage: 'ConfigurationOfRefactoringTools';<br>> install.<br>> (Smalltalk at: #ConfigurationOfRefactoringTools) project load: '2.0'.<br>> <br>> The #stable symbolic version will work only after the release because Metacello matches "alpha" versions to previous versions. So 'squeak5.3.x' and 'squeak5.2.x' will match to "Squeak5.3alpha". .... -.-"<br>> <br><br>Yea, I wrote that ;P<br><br><br>> Best,<br>> Marcel<br>>> Am 03.09.2019 06:56:26 schrieb tim Rowledge <tim@rowledge.org>:<br>>> <br>>> <br>>> <br>>> > On 2019-09-02, at 8:31 PM, Chris Muller wrote:<br>>> > <br>>> > Hi Tim,<br>>> > <br>>> > As a general point I'd like to throw down a (small) marker for the idea of incorporating the Refactoring tools in the standard image. We make a big deal of the importance of refactoring code and the way that Smalltalk's tools help do that, but quite a few important refactoring actions are pretty tricky in the standard tools. I'd argue that the integration of the refactoring tools (the menus particularly) could be improved, but still.<br>>> > <br>>> > Even though I love and use the refactoring tools for development, they bring too much "weight" to the image and IDE for new and general, non-developer users. In particular, it adds quite a few extra menu entries which are of only interest to developers doing development. It's 10X easier for a developer to load the package than for a anyone to unload. -1<br>>> <br>>> I have considerable sympathy for your view, really. I suspect - based on a fairly quick scan of the code, nothing more - that quite a lot could be removed by integrating better into the core of Squeak. There seem to be plenty of classes duplicating extant functionality, at a guess as part of making the code fit many systems. And the integration into the browser menus is, frankly, horrible. Then again, there are *already* way too many poorly thought out menu entries in the browsers. I wish we had the resources to provide the refactoring assistance in a cleaner, better integrated, manner<br>>> <br>>> tim<br>>> --<br>>> tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>>> You never really learn to swear until you learn to drive in Silicon Valley<br>>> <br>>> <br>>> <br>> <br><br><br><br></tim@rowledge.org></marcel.taeumel@hpi.de></div></blockquote>
</div></body>