<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
Hi Hilaire,<br>
<br>
<br>
<div class="moz-cite-prefix">On 8/3/21 11:16 AM, Hilaire Fernandes
via Cuis-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c72ecd2c-55cb-0abc-f8fb-fbc7a32f8474@drgeo.eu">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="+1">Hi Nicola, <br>
</font></p>
<p><font size="+1">What I am guessing: the start up script invoked
with the -s command ran in a process of higher priority than
the UI process -- where the morph operations occur.</font></p>
</blockquote>
<br>
that might well be ! <br>
<br>
<blockquote type="cite"
cite="mid:c72ecd2c-55cb-0abc-f8fb-fbc7a32f8474@drgeo.eu">
<p><font size="+1">Sending the message #doOneCycle is forcing one
loop of update of the UI, i.e. the requested Morphic
operations are forced to take place immediately (mostly?)</font></p>
<p><font size="+1">Your forked process, with the delay, just
delays your Morphic operations once the start up script has
been entirely executed -- or something like that.</font></p>
<p><font size="+1">I should add a note in the ad-hoc book section,
but I don't understand fully the evolution of the issue -- was
working with previous image and not anymore now if the
#doOneCycle message is not send.</font></p>
<p><font size="+1">I opened an issue <a
class="moz-txt-link-freetext"
href="https://github.com/Cuis-Smalltalk/TheCuisBook/issues/15"
moz-do-not-send="true">https://github.com/Cuis-Smalltalk/TheCuisBook/issues/15</a>
to not forget about it.</font></p>
<p><font size="+1">Feel free to add comment to this issue when
needed so we can fix the documentation appropriately.<br>
</font></p>
</blockquote>
<br>
I find putting notes in Git issues is great not to forget ! <br>
<br>
I consider documentation fundamental. I learnt most of what i know
by book, i love them ;)<br>
I am willing to give you an hand on that.<br>
<br>
For the moment I need to leave aside the boot issue, but I will be
back. <br>
<br>
In particular, a have a raw vision by now, but I think it would be
great if we could implement<br>
things in such a way that: <br>
<br>
. ENV parameters must be read before anything and must be able to
set global variables / Preferences.<br>
. string parameter must be executed with high priority, maybe before
the World goes up ? <br>
. script parameters must be executed when everything else is done.<br>
<br>
I am going to copy this into the git, near your comment, even if it
is not about<br>
documentation but about the same issue.<br>
<br>
Bye<br>
Nicola<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>