<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Chris,<div><br></div><div>thanks for these suggestions. One major concern is to use *as little code as possible* like in the emergency evaluator. Let's see what's possible in this regard.</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;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 16.05.2019 00:26:22 schrieb Chris Muller <asqueaker@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi Marcel,
<br>
<br>Great idea to improve the Interrupt! function. I would eschew a
<br>Boolean preference for a kind of "handler" that could be selected such
<br>as;
<br>
<br> 1) presents the menu you presented (or a custom menu),
<br> 2) traditional Smalltalk IDE behavior (no pre menu),
<br> 3) showing a list of processes to select and act on,
<br> 4) nothing, completely disabled (user production system), or
<br> 5) something customizable like #3 for production system, but also
<br>write a log file to disk or network for customer support..or maybe
<br>increment a counter for usage tracking (to answer the question, "how
<br>often are people feeling the need to interrupt"), etc.
<br>
<br>> - How might a possible extension point look like to add a domain-specific clean-up rule? or is #cleanUp: enough?
<br>
<br>Another good idea of something to try to standardize on. Seems like
<br>multiple frameworks have #cleanUp:, doesn't it? A registry of some
<br>kind where apps can add which classes they want sent #cleanUp:
<br>whenever that menu item is selected (or event triggered) would be
<br>nice. Class-side #cleanUp:'s are good places, since they're the
<br>objects responsible for making instances in the first place. I
<br>definitely wouldn't recommend anything like enumerating class
<br>hierarchy and sending #cleanUp:, though. Only registered. Full
<br>control.
<br>
<br>Best,
<br> Chris
<br>
<br>
<br>On Wed, May 15, 2019 at 11:59 AM Marcel Taeumel <marcel.taeumel@hpi.de> wrote:
<br>>
<br>> Hmm... maybe this kind of feedback:
<br>>
<br>> - Should it be a preference or the default way of CMD+Dot?
<br>> - What entries would you like to see in this list by default?
<br>> - How might a possible extension point look like to add a domain-specific clean-up rule? or is #cleanUp: enough?
<br>>
<br>> Best,
<br>> Marcel
<br>>
<br>> Am 15.05.2019 18:46:36 schrieb Chris Cunnington <brasspen@gmail.com>:
<br>>
<br>> This is interesting. I wanted to add a Load Abort button to ScriptBook, but I realized that you can’t press a button in the UI when something is loading. The only way to stop it is CMD+Dot. Initially I thought I’d have a button that did what CMD+Dot did, but for the life of me I couldn’t see how that worked. I’m glad to see it so clearly illustrated. As it works, I’m not sure what kind of feedback you’re looking for here. But if you’re polling to see if people think it’s a good idea, then you have my vote.
<br>> +1
<br>>
<br>> Chris
<br>>
<br>> On May 15, 2019, at 10:47 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:
<br>>
<br>> Hi, there.
<br>>
<br>> Please find attached a changeset. It represents a quick prototype to make the CMD+Dot command more powerful. One might extend it to provide user-friendly, domain-specific clean-up or restarts of applications.
<br>>
<br>> <image.png>
<br>>
<br>> Best,
<br>> Marcel
<br>> <cmd-dot-dialog.1.cs>
<br>>
<br>>
<br>>
<br></cmd-dot-dialog.1.cs></image.png></marcel.taeumel@hpi.de></brasspen@gmail.com></marcel.taeumel@hpi.de></div></blockquote>
</div></body>