<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Hilaire,<br>
<br>
On 5/20/2024 9:56 AM, Hilaire Fernandes via Cuis-dev wrote:
<blockquote cite="mid:62e8227f-1fa8-46e3-81d3-f72eb2a48c1d@free.fr"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Le 13/05/2024 à 22:00, Juan Vuletich
via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite" cite="mid:6642714E.7080401@cuis.st">I've
just created a new repo for Cuis 7.0. This is the beta phase of
the release, where we can do QA and fix any issues. <br>
</blockquote>
<p>Does this stable release 7.0 capture the state of the third
party packages?<br>
</p>
</blockquote>
<br>
One of the objectives of the stable releases is to offer a higher
level of quality than the rolling release. Only packages that are
well maintained and known to work should be considered part of the
stable release. The packages that I have already included are the
ones I thought reasonable to assume to be in a good enough shape.<br>
<br>
<blockquote cite="mid:62e8227f-1fa8-46e3-81d3-f72eb2a48c1d@free.fr"
type="cite">
<p> </p>
<p>Stable release 6.2 did not work for DrGeo, because third party
packages were kept compatible with 6.3 with no version for 6.2<br>
</p>
<p>We discussed that at that time.<br>
</p>
</blockquote>
<br>
Which other packages do you need for DrGeo? We'd review them for
quality, and add them. I really need to know this in order to be
able to help.<br>
<br>
<blockquote cite="mid:62e8227f-1fa8-46e3-81d3-f72eb2a48c1d@free.fr"
type="cite">
<p> </p>
<blockquote type="cite" cite="mid:6642714E.7080401@cuis.st"> <br>
Official release of Cuis 7.0 will be on May 31st. <br>
<br>
The rolling release of Cuis has been bumped to 7.1. <br>
</blockquote>
<p>I have small issue with 7.1 and my configuration script to
install my development environment. For the record the script is
executed from the a Bash script with -s flag to the VM.</p>
<p>In my configuration script, I setup VM to fullscreen, however
now the fullscreen resize is effective only later, therefore the
RealEstateAgent information of screen area is wrong. The usable
area is set to a smaller surface, the default one of the VM
window I guess.<br>
</p>
<p>See part of the script:<br>
</p>
<p> (Delay forSeconds: 1) wait.<br>
UISupervisor whenUIinSafeState: [<br>
(world submorphs reject: [:aMorph | aMorph is:
#TaskbarMorph])<br>
do: [:each | each delete].<br>
"Adjust font size"<br>
Preferences at: #defaultFontSize put: 10.<br>
"Adjust taskbar size"<br>
morph := world taskbar.<br>
morph scale: 1/2.<br>
<b> Display fullScreenMode: true.</b><br>
"Compute the available free space for windows placement"<br>
area := RealEstateAgent maximumUsableArea extendBy: 0 @
morph morphHeight negated.<br>
extent := area extent // 2.<br>
"Open a few System Browsers"<br>
Browser open <br>
morphPosition: 0@0;<br>
morphExtent: extent.<br>
</p>
<p><br>
</p>
<p>Any idea?<br>
</p>
</blockquote>
<br>
You say "now the fullscreen resize is effective only later". Is this
due to changes in the Linux startup script? The only relevant
changes to that file are<br>
<a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/commit/2ef28c221e5db84b05f849141896222b971c611f#diff-829ae88058002c7284027f40ba713fc097831538a4e5339ef17901ed3d7f9f66">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/commit/2ef28c221e5db84b05f849141896222b971c611f#diff-829ae88058002c7284027f40ba713fc097831538a4e5339ef17901ed3d7f9f66</a><br>
and<br>
<a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/commit/09a1340e7bc19d88b88a6c71e0e924b3498dfc77">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/commit/09a1340e7bc19d88b88a6c71e0e924b3498dfc77</a><br>
You can experiment with them.<br>
<br>
Or the reason is some update to the Cuis image? If so, can you
isolate the change set that generates this behavior? It should be
something after the last 6.3RR on which you were able to run your
configuration script. You may try loading them in batches, and find
out which one is responsible.<br>
<br>
<br>
HTH.<br>
<br>
<blockquote cite="mid:62e8227f-1fa8-46e3-81d3-f72eb2a48c1d@free.fr"
type="cite">
<p> </p>
<pre class="moz-signature" cols="72">--
GNU Dr. Geo
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://gnu.org/s/dr-geo/">http://gnu.org/s/dr-geo/</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://gnu-drgeo.blogspot.com/">http://gnu-drgeo.blogspot.com/</a></pre>
</blockquote>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich</pre>
</body>
</html>