<div dir="ltr">Note that we can still override a .mcm when needed.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 12 janv. 2022 à 14:44, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de">marcel.taeumel@hpi.de</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="gmail-m_4820488089774778620__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);text-align:left" dir="ltr">
> <span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">The problem that I see with this strategy is that users that do not explicitly try out all new defaults will be surprised by them lately only when they try out a newly released image.</span><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px"><br></span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">Ehm... yeah. That's not the process of testing a new release build. ;-) You download the new bundle and test that. Your local work image can have all kinds of quirks not present in the release bundle.</span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px"><br></span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">> </span><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">I'm sorry for the misunderstanding. Shall I revert this?</span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px"><br></span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">I assume that you did add an update-map entry already? Then it's too late. If not, sure, revert it.</span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px"><br></span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">Best,</span></div><div><span style="font-family:Calibri,Helvetica,sans-serif;font-size:16px">Marcel</span></div><div></div>
<blockquote 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:rgb(170,170,170);margin-top:10px">Am 12.01.2022 14:41:21 schrieb Thiede, Christoph <<a href="mailto:christoph.thiede@student.hpi.uni-potsdam.de" target="_blank">christoph.thiede@student.hpi.uni-potsdam.de</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div id="gmail-m_4820488089774778620divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr">
<p>Hi Marcel,</p>
<p><br>
</p>
<p>I'm sorry for the misunderstanding. Shall I revert this?</p>
<p><br>
</p>
<p>The problem that I see with this strategy is that users that do not explicitly try out all new defaults will be surprised by them lately only when they try out a newly released image. If all preference variables were only set to a value different from nil
when a user *explicitly decides* to change it, it would be easier for us to change the behavior for the rest of the users only.</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_4820488089774778620divRplyFwdMsg" dir="ltr"><span style="font-family:Calibri,sans-serif;color:rgb(0,0,0)"><b>Von:</b> Squeak-dev <<a href="mailto:squeak-dev-bounces@lists.squeakfoundation.org" target="_blank">squeak-dev-bounces@lists.squeakfoundation.org</a>> im Auftrag von Taeumel, Marcel<br>
<b>Gesendet:</b> Mittwoch, 12. Januar 2022 14:18:12<br>
<b>An:</b> squeak-dev<br>
<b>Betreff:</b> Re: [squeak-dev] The Trunk: Morphic-ct.1843.mcz</span>
<div> </div>
</div>
<div>
<div id="gmail-m_4820488089774778620__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);text-align:left" dir="ltr">
Hi Christoph --
<div><br>
</div>
<div>This is what I meant what we should not do. We should not change the preferences a user currently has in his or her image through the update stream. Just because we agreed on a different default value, we must not change what users decided before that.
:-( Please don't do that again in the future. :-) We only synchronize those preferences in the release-building process.</div>
<div><br>
</div>
<div>Best,</div>
<div>Marcel</div>
<div></div>
<blockquote 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:rgb(170,170,170);margin-top:10px">Am 10.01.2022 17:29:45 schrieb <a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a> <<a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a>>:</p>
<div style="font-family:Arial,Helvetica,sans-serif">Christoph Thiede uploaded a new version of Morphic to project The Trunk:<br>
<a href="http://source.squeak.org/trunk/Morphic-ct.1843.mcz" target="_blank">http://source.squeak.org/trunk/Morphic-ct.1843.mcz</a><br>
<br>
==================== Summary ====================<br>
<br>
Name: Morphic-ct.1843<br>
Author: ct<br>
Time: 10 January 2022, 5:29:01.402518 pm<br>
UUID: c969959b-377b-aa41-a85a-b4ffc3239a2d<br>
Ancestors: Morphic-ct.1841<br>
<br>
Synchronizes default preference value for "Enclose selection with brackets". Complements Morphic-mt.1812.<br>
<br>
=============== Diff against Morphic-ct.1841 ===============<br>
<br>
Item was changed:<br>
(PackageInfo named: 'Morphic') postscript: '"Fix missing command key shortcuts such as [cmd]+[+/-] for scale changes."<br>
Project allMorphicProjects do: [:p | p world initializeDesktopCommandKeySelectors].<br>
<br>
"New ''scale factor'' menu"<br>
+ TheWorldMainDockingBar updateInstances.<br>
+ <br>
+ "Enable ''Enclose selection with brackets'' by default (Morphic-mt.1812)"<br>
+ TextEditor encloseSelection: true.'!<br>
- TheWorldMainDockingBar updateInstances.'!<br>
<br>
<br>
</div>
</blockquote>
</div>
</div>
</div></blockquote></div><br>
</blockquote></div>