<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
<p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px">> Is LayoutFrame fractions: (0.25@0 corner: <a href="mailto:0.5@0.42" title="Neue Nachricht an 0.5@0.42" style="cursor: pointer; color: blue;">0.5@0.42</a>) offsets: (4@0 corner: 0@ -20) actually harder to read than a LayoutFrame( l 0.25+4 t 0+0 r 0.5+0 b 0.42-20 ) ?</p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br></p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Yes, because it separates left fraction + left offset (etc.) visually. Again, the current printOn: reflects my personal debugging needs. :-) No, #printOn: does not have to be evaluable. We use #storeOn: for that. Until recently, #printOn: wasn't even implemented in LayoutFrame. Feel free to improve it for reasons other than evaluability. ;-)</p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br></p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Do you want to have a "print it" shortcut for #storeString? Like "store it"? Like CMD+SHIFT+P instead of CMD+P? That might be a nice productivity tool...</p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px"><br></p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Best,</p><p style="margin-top: 0px;margin-bottom: 0px;font-family: Calibri, Helvetica, sans-serif;font-size: 16px">Marcel</p><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 18.09.2019 16:15:19 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size: 12pt;color: #000000;font-family: Calibri,Helvetica,sans-serif" dir="ltr">
<p>Hi Marcel,</p>
<p><br>
</p>
<p>actually I find re-evaluability quite often useful - for example, when I would like to take the LayoutFrame and set it to another Morph. At the moment you need to totally deconstruct + rewrite the expression to reuse it, while on the other hand you can directly
print-and-eval points and rectangles. For beginners, it also helps to understand how the Objects are created.</p>
<p><br>
</p>
<p>Is</p>
<p><span>LayoutFrame fractions: (0.25@0 corner: 0.5@0.42) offsets: (4@0 corner: 0@ -20)</span></p>
<p><span>actually harder to read than</span></p>
<p><span><span>a LayoutFrame( l 0.25+4 t 0+0 r 0.5+0 b 0.42-20 )</span><br>
</span></p>
<p><span><span>?</span></span></p>
<p><span><span>(Imho, the latter with the unfamiliar non-Smalltalk syntax looks much more confusing to me. :) )</span></span></p>
<p><br>
</p>
<p><span><span>Best,</span></span></p>
<p><span><span>Christoph</span></span></p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif;font-size: ;margin: 0">
<div><span style="font-size: 10pt;color: #808080"></span></div>
</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif;color: #000000"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel<br>
<b>Gesendet:</b> Mittwoch, 18. September 2019 13:54:55<br>
<b>An:</b> Alan Grimes via Squeak-dev<br>
<b>Betreff:</b> Re: [squeak-dev] LayoutFrame>>#printOn:</span>
<div> </div>
</div>
<div>
<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Christoph,
<div><br>
</div>
<div>I recently changed that to be more valuable for me when debugging layout issues. Feel free to add more "ifNil" checks if needed - there are already some.</div>
<div><br>
</div>
<div>However, there is no need to make that string re-evaluable. It's designed to fit the human eye. At least mine. :-)</div>
<div><br>
</div>
<div><img width="auto" src="cid:47ce2d0b-1951-46cb-b1d6-e433f6d1655a"></img><!-- </img> --></div>
<div><br>
</div>
<div>Best,</div>
<div>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;">Am 18.09.2019 13:50:09 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p>
<div style="font-family:Arial,Helvetica,sans-serif">
<div id="divtagdefaultwrapper" style="font-size: 12pt;color: #000000;font-family: Calibri,Helvetica,sans-serif" dir="ltr">
<p>Hi all,</p>
<p><br>
</p>
<p>is anyone attached to the current <span>LayoutFrame>>#printOn: design?</span></p>
<p><span>The current one fails if some instvars are nil. This is the case for SystemWindowButtons.</span></p>
<p><span>Furthermore, I never liked the current string representation, it has a quite cryptic look and does not match the common way you create a LayoutFrame using #fractions:/#offsets:.</span></p>
<p><span><br>
</span></p>
<p><span>Would anyone mind me to rewrite #printOn: in order to return a re-evaluatable string? Are there any dependencies?</span></p>
<p><span><br>
</span></p>
<p>Best,</p>
<p>Christoph</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif;font-size: ;margin: 0">
<div><span style="font-size: 10pt;color: #808080"></span></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div></blockquote></div>