<!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 Gerald,<br>
<br>
I wish you and everyone in our community a great 2024!<br>
(inline)<br>
<br>
On 12/30/2023 12:03 PM, Gerald Klix via Cuis-dev wrote:
<blockquote cite="mid:702919b6-c8e2-3fd8-bfbb-4a5c358fb9b4@klix.ch"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Hi Juan,<br>
<br>
sorry for the long delay, I caught a rather nasty cold.<br>
<br>
First and most important:<br>
<b>Thank your for your work!</b><br>
</div>
</blockquote>
<br>
You're most welcome!<br>
<br>
<blockquote cite="mid:702919b6-c8e2-3fd8-bfbb-4a5c358fb9b4@klix.ch"
type="cite">
<div class="moz-cite-prefix"> Second and less important:<br>
Haver's image saving problems are gone with Cuis Version 6.2 and
6.3.<br>
There are some minor issues like<br>
<ul>
<li>a different order of menu items in the preference menu
(trivial to fix)</li>
<li>font loading, the <tt>TrueTypeFonts</tt> directory is not
found in my setup (easy to fix)<br>
</li>
</ul>
<br>
For the remainder, please see my inline comments.<br>
<br>
<br>
Best Regards,<br>
<br>
Gerald<br>
</div>
</blockquote>
<br>
Yeah. As usual, some minor bumps may happen. Of course, keep
reporting serious trouble or annoyances!<br>
<br>
<blockquote cite="mid:702919b6-c8e2-3fd8-bfbb-4a5c358fb9b4@klix.ch"
type="cite">
<div class="moz-cite-prefix"> ... <br>
</div>
IC, to describe the situation in German: „Einen Tod muß man
sterben.“, meaning you have to choose one evil.<br>
<br>
I can only think of one – rather nifty – improvement:<br>
Add two preference menu options like:<br>
<br>
'Save preferences globally'<br>
This one selects the currently implemented behavior.<br>
<br>
'Save preferences only in image'<br>
This one implements the old behavior.<br>
<br>
Both will be persisted in <tt>UsersPrefs.txt</tt>. The later<br>
serves as a flag, that means: Ignore every other setting in <tt>UserPrefs.txt</tt>
and<br>
stick to the settings that are already persistent in the image.<br>
</blockquote>
<br>
I did something very much like that. Thanks for the suggestion!<br>
Check the updated Preferences menu.<br>
<br>
<blockquote cite="mid:702919b6-c8e2-3fd8-bfbb-4a5c358fb9b4@klix.ch"
type="cite">....<br>
<blockquote type="cite" cite="mid:65858148.9040904@cuis.st"> <br>
It also means to try to give a platform agnostic experience. For
instance, right now, I'm doing a kind of introductory curse to
CS for my daughters and a few friends (teenagers and young
adults). I prepared a bunch of thumbdrives with this very Cuis
setup. They bring a mix of Windows, Intel and ARM Mac, and Linux
laptops. This works on all of them without needing to waste
their attention on irrelevant technicalities. I like that, and I
think it reflects the kind of experience most novices will have.
<br>
</blockquote>
Nice, I tried such a thing for two of my daughters individually
and two of my sons.<br>
I failed miserably.<br>
I hope you are better at teaching, than I am!<br>
</blockquote>
<br>
I'm don't think I'm much at a teacher, but I'm trying!<br>
<br>
I'm calling this "Computadoras y Números" (Computers and Numbers).
I'm trying to help them develop some algorithm thinking, and
understand how computers deal with numbers and how we can get them
to compute useful stuff. Even though we are using Cuis, I didn't
even bother to explain Smalltalk syntax, just jumping into "the
stuff".<br>
<br>
For the first session, I wanted them to compute the square root of
an integer number. We talked for some minutes about what does that
mean, and how that could be computed. Then I let them try it, and
help them as they move along. The next exercise was to use the trick
that adding consecutive odd numbers yield perfect squares, and
compare both methods. It went OK, but it was a bit too hard for
them.<br>
<br>
For the second session I wanted to play with real numbers, so we
tried two ways of computing Pi. The first one was to "draw" a circle
on a grid, and take the number of points in the grid that lie inside
the circle (using the x^2+y^2 <= r formula), divide that by the
total number of points. And do that for increasingly larger grids,
to improve the approximation. This one is interesting because it
only uses integers. But it is slow. Then we tried another method,
that is the perimeter of an inscribed polygon of increasing number
of sides. This later one can be done without trigonometry, but it
requires sqrt() to normalize the vertexes, hence Float. These are
way more complicated things that what we did before, so I went
slower, and explained my solution on my computer as I guided them on
writing their own. So I didn't push them too much and they didn't
get frustrated. I guess the ability to write the solution completely
on their own requires a bit more time and practice, and my objective
is to engage them, not scare them. They still could really
understand what we were doing, and appreciate the kind of thinking
involved.<br>
<br>
It was a lot of what Alan calls "hard fun". I'm looking forward for
our next session!<br>
<br>
<br>
<br>
<blockquote cite="mid:702919b6-c8e2-3fd8-bfbb-4a5c358fb9b4@klix.ch"
type="cite">... Suppose you want to write a maintenance
application<br>
for images – something I am contemplating for years – a straight<br>
forward solution is to use directories in the filesystem to
structure<br>
a given set of tuples of image and change files. The current
solution<br>
forces the maintenance application to copy (or symlink)<br>
<tt>UnicodeData.txt</tt> and the file with the compressed
sources.<br>
<br>
How about an 'image (related) data directory', that<br>
contains all that stuff? There should be command line options
similar<br>
to those implemented for the <tt>userBaseDirectory</tt>.<br>
<br>
The TrueTypeFonts directory seems to be already relative to the <tt>userBaseDirectory</tt>,<br>
which is, IHMO, is the best solution.<br>
</blockquote>
<br>
We could use a preference for the directory containing sources and
UnicodeData.txt. Or we could store them in the #vmPath. Or just keep
them in the same directory as the image. I really don't see much of
a problem.<br>
<br>
Cheers,<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>