<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Keep it as simple as possible. Re-use and apply the UI that is already there. :-)<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;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 15.02.2020 19:47:02 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size: 12pt;color: #000000;font-family: Calibri,Helvetica,sans-serif">
> <span style="font-size: 12pt">Not sure I understand this correctly... is the requirement that you </span><span style="font-size: 12pt">should be able to type right away without accidentally overwriting the </span><span style="font-size: 12pt">boilerplate code
of the operation? The surrounding block and its </span><span style="font-size: 12pt">arguments in this case.</span>
<div><br>
</div>
<div>This is correct.</div>
<div><br>
</div>
<div>> <span style="font-size: 12pt">Just mention the variable names that can be used in the </span><span style="font-size: 12pt">prompt.</span></div>
<div><span style="font-size: 12pt"><br>
</span></div>
<div><span style="font-size: 12pt">Hm ... This feels like a workaround ... For true Smalltalkers, it should be easier to understand a code signature than actually reading natural language.</span></div>
<div><span style="font-size: 12pt"><br>
</span></div>
<div><span style="font-size: 12pt">> </span><span style="font-size: 12pt">This makes them fix, but is it necessary to be able to change </span><span style="font-size: 12pt"></span><span style="font-size: 12pt">them?</span><span style="font-size: 12pt">
<div><br>
</div>
<div>At least it would be a cool feature, or would it be <i>too</i> cool?</div>
</span></div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_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 Jakob Reschke <forums.jakob@resfarm.de><br>
<b>Gesendet:</b> Samstag, 15. Februar 2020 18:02:01<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] Changeset: requestCode.cs</span>
<div> </div>
</div>
</div>
<span style="font-size: 10pt"><span style="font-size: 10pt">
<div class="PlainText">Am Sa., 15. Feb. 2020 um 17:30 Uhr schrieb Thiede, Christoph<br>
<Christoph.Thiede@student.hpi.uni-potsdam.de>:<br>
><br>
> Marcel gave the germane critique that such dialogs should preserve the possibility to replace the initial selection with a custom filter, without caring about any header, what's not possible with arguments at the moment.<br>
><br>
<br>
Not sure I understand this correctly... is the requirement that you<br>
should be able to type right away without accidentally overwriting the<br>
boilerplate code of the operation? The surrounding block and its<br>
arguments in this case.<br>
<br>
If you just want an expression, why indicate asking for a complete<br>
method text? If you avoid that, the question about ^ or not can be<br>
avoided. Just mention the variable names that can be used in the<br>
prompt. This makes them fix, but is it necessary to be able to change<br>
them?<br>
<br>
</div>
</span></span>
</div></blockquote>
</div></body>