<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hi Dave,</p>
<p><br>
</p>
<p>I don't see your point. I already have eliminated ActiveWorld, ActiveHand, and ActiveEvent *are* in the Trunk, are you talking about the #currentWorld, #currentHand, and #currentEvent senders? :-)</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">
<div class="x__rp_U4 x_ms-font-weight-regular x_ms-font-color-neutralDark x_rpHighlightAllClass x_rpHighlightBodyClass" id="x_Item.MessageUniqueBody" style="font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont">
<div dir="ltr">
<div id="x_divtagdefaultwrapper"><font face="Calibri,Helvetica,sans-serif,EmojiFont,Apple Color Emoji,Segoe UI Emoji,NotoColorEmoji,Segoe UI Symbol,Android Emoji,EmojiSymbols">
<div id="x_Signature">
<div style="margin:0px"><font style="font-family:Calibri,Arial,Helvetica,sans-serif,serif,EmojiFont">
<div><font size="3" color="black"><span style="font-size:12pt"><a href="http://www.hpi.de/" target="_blank" rel="noopener noreferrer" id="LPNoLP"><font size="2"><span id="LPlnk909538"><font color="#757B80"></font></span></font></a></span></font></div>
</font></div>
</div>
</font></div>
</div>
</div>
</div>
</div>
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von David T. Lewis <lewis@mail.msen.com><br>
<b>Gesendet:</b> Dienstag, 17. November 2020 02:11:22<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] Worlds in Worlds are NOT completely dead?! ????</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Christoph,<br>
<br>
On Mon, Nov 16, 2020 at 03:31:47PM +0000, Thiede, Christoph wrote:<br>
> Hi Dave,<br>
> <br>
> eliminating further globals is definitively always a desirable goal, but<br>
> are you referring to any certain domain? It looks as if the most problematic<br>
> portions of global state resist in the Project/Process logic themselves.<br>
<br>
<br>
The four globals of interest are:<br>
<br>
- World. This has already been cleaned up, and the global World remains<br>
only for support of external packages or projects that have references<br>
to it. For a trunk image, the global can be removed without issue.<br>
<br>
- ActiveWorld. This is meaningful only to a Morphic project and<br>
presumably can be refactored to eliminate the global.<br>
<br>
- ActiveHand. This is meaningful only to a Morphic project and<br>
presumably can be refactored to eliminate the global.<br>
<br>
- ActiveEvent. This is probably global to the system, and it may<br>
be appropriate to leave it as a global variable.<br>
<br>
My opinion - ActiveWorld looks like the next thing to eliminate<br>
if possible. It is clearly related to World, and figuring out why<br>
ActiveWorld needs to exist would be the next problem to solve.<br>
<br>
After that, ActiveHand would be then next thing to look at. It is<br>
specific to Morphic, and it is not clear what it should mean in<br>
the context of World in World, or in mixed Morphic and MVC projects.<br>
<br>
Finally, ActiveEvent might need attention. I would rate this as<br>
low priority, and there may not be anything wrong with the current<br>
use of global state for ActiveEvent.<br>
<br>
> For example, should we have one user interrupt watcher per project, and<br>
> how should be decided which of them is activated if there is an MVC embedded<br>
> into a Morphic project? Questions over questions :-)<br>
> <br>
<br>
The user interrupt watcher exists at a lower level. I think (but am<br>
not certain) that it needs to be this way. The event that triggers<br>
the user interrupt watcher is processed through the VM, and by the<br>
time the VM finds out about the user interrupt request, it does not<br>
have any easy way to know about the Process the user request was<br>
intended to interrupt.<br>
<br>
So no, I don't think that this should be handled on a per-Project<br>
basis. The key thing is to know (or deduce) what Process needs to<br>
be interrupted, and it probably does not much matter what Project<br>
context the interrupt is handled in.<br>
<br>
Dave<br>
<br>
<br>
</div>
</span></font>
</body>
</html>