<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Tim --<div><br></div><div>> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">I also tried using Git Browser for the above. But unfortunately, Git Browser</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> seems bitten by the 60Deprecation also ( #ifNotNilDo: ), and does not work</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> very well in 6.0beta. Will Git Browser be updated for this deprecated-method-</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> removal before release?</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">I hope that Jakob will make another release of the Git Browser for Squeak 6.0.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Anyway, we plan to have </span><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">60Deprecated loaded by default soon again. It was</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">a nice little experiment and we learned something from it. :-)</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">You can try the latest development version of the Git Browser by changing the</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">url in Installer >> #installGitInfrastructure to:</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif"><span style="font-size: 13px">github://hpi-swa/Squot:develop/src</span></span><br></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif"><span style="font-size: 13px">instead of</span></span></div><div><span style="font-family: Arial, Helvetica, sans-serif"><span style="font-size: 13px"><br></span></span></div><div><span style="font-family: Arial, Helvetica, sans-serif"><span style="font-size: 13px">github://hpi-swa/Squot:latest-release/src</span><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><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;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 10.06.2022 03:21:31 schrieb Tim Johnson <digit@sonic.net>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi Marcel,<div class=""><br class=""></div><div class="">I have not been following the discussion re: 60Deprecated. (I suspect 60Deprecated is a special case because it has been in images for a few releases already now?)</div><div class=""><br class=""></div><div class="">If Squeak 6.0 wants to be released with Seaside loadable in it, then this may be a question of release schedules and resourcing.</div><div class=""><br class=""></div><div class=""><div class="">Agreed that the future-proof solution here is to make these changes in Seaside-Squeak-Core and Seaside-Squeak-Continuation. And, to retain backwards compatibility, the proper change is probably to move the ContextPart & BlockContext extension methods to new packages: Seaside-Squeak5-Core and Seaside-Squeak5-Continuation. Then, edit the BaselineOfSeaside3 spec to include those packages on squeak4.x and squeak5.x.</div></div><div class=""><br class=""></div><div class="">I started working on a commit with these changes. Unfortunately, when I tried to commit these to my FileTree repo containing my local fork, Monticello was telling me that WAPharoEncoder methods had been removed. No idea why. I need to try again with a fresh fork and a fresh image.</div><div class=""><br class=""></div><div class="">I also tried using Git Browser for the above. But unfortunately, Git Browser seems bitten by the 60Deprecation also ( #ifNotNilDo: ), and does not work very well in 6.0beta. Will Git Browser be updated for this deprecated-method-removal before release?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="EFDBB6C3-09B0-4E0F-961D-8C8C3590E1D1" src="cid:3836657F-4D71-4290-8720-1B5493010421@gateway.sonic.net" class=""></img></div><div class=""><br class=""></div><div class="">Thanks, </div><div class="">Tim J</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class="" style="min-width: 500px"><div class="">On Jun 9, 2022, at 1:59 AM, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" class="">marcel.taeumel@hpi.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;text-align: left" dir="ltr" class="">
Hi Tim --<div class=""><br class=""></div><div class="">Interesting. So, would it really make sense to have 60Deprecated already loaded in the release image? I think it would be better to fix these issues. At least in 6.1, I do not want to have 60Deprecated loaded anymore by default. People should opt-in for that.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Marcel</div><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;min-width: 500px"><p style="color: #AAAAAA; margin-top: 10px;" class="">Am 05.06.2022 02:50:36 schrieb Tim Johnson <<a href="mailto:digit@sonic.net" class="">digit@sonic.net</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif" class="">Hi all,<br class=""><br class="">Just FYI — <br class=""><br class="">I went through loading Seaside in 6.0beta-#21848. (Metacello loading is so fast now! Great job and thank you!)<br class=""><br class="">There are two places where the BlockContext family retirement will break Seaside loading. One is a rendering method but the other is in continuations. I've filed issues on the Seaside GitHub project. It's clear that if we want these fixed, we will have to do it ourselves.<br class=""><br class=""><a href="https://github.com/SeasideSt/Seaside/issues/1314" class="">https://github.com/SeasideSt/Seaside/issues/1314</a><br class="">https://github.com/SeasideSt/Seaside/issues/1315<br class=""><br class="">BaselineOfSeaside3>>#baselinesqueak: would be a good place to begin splitting out the new requirements for Squeak 6.0 compared to earlier versions. I don't know that /this/ list is the proper place to have much discussion about this, but I thought I'd mention it here.<br class=""><br class="">Thanks,<br class="">Tim J<br class=""><br class=""><br class=""><br class=""></div></blockquote></div><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div>