<div dir="ltr"><div dir="ltr">Oh! About what <a class="gmail_plusreply" id="plusReplyChip-0" href="mailto:hfern@free.fr" tabindex="-1">@Hilaire Fernandes</a> mentioned: maybe we can detect the user's OS and provide a download link matching that?</div><div>I've seen that work on many websites.</div><div><br></div><div>Best,</div><div>Nico PM</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 24, 2023 at 3:20 PM Nicolás Papagna Maldonado <<a href="mailto:nicolas.papagna@gmail.com">nicolas.papagna@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi folks!<div><br></div><div>I didn't have the chance to test this yet.</div><div>I have one question: will this distribution log things to the all-in-one folder?</div><div><br></div><div>I believe this is important for newcomers, in case they find any issues and need to send those to the mailing list.</div><div><br></div><div>Cheers,</div><div>Nico PM </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 24, 2023 at 3:03 PM Hilaire Fernandes via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div bgcolor="#FFFFFF">
<p><font size="4">Hi Juan & al,</font></p>
<p><font size="4">I am just catching up.</font></p>
<p><font size="4">This is always a good idea to ease the start-up
experience to new </font><font size="4"> Cuis-Smalltalk </font><font size="4">users. I am sure it will have important impact. I
tested on Ubuntu 23.10, it works smoothly.</font></p>
<p><font size="4">Regarding all-in-one application, I have been
using it a lot in the past with Dr. Geo, then at some point
stopped using it. I stopped for technical reasons, but then I
realized there were also end user reasons to stop using it. </font></p>
<p><font size="4">Indeed, it adds complexity that does not serve the
end user. For example, a Linux user will see VM, scripts for the
Windows user. Will this Linux user uses this same folder
structure to execute Cuis on a Windows machine? No, because he's
using Linux. Then it does not scale very well. Will you add VM
for Linux on Arm, on RiscV? Then we can argue the same with
image, why both 64bits and 32bits, the end user will only use
one variant of it.<br>
</font></p>
<p><font size="4">The truth about all-in-one application is it makes
the life easier for the developers and people deploying end-user
applications, like me with DrGeo. You just need to upload one
package and that's it. In a such momentum, we should realize it
is not a good sign, we are not serving the end-user first, but
ourself.<br>
</font></p>
<p><font size="4">What will be make life easier for end user is an
archive to download containing the VM and the image it needs.
That's it.<br>
</font></p>
<p><font size="4">I will use your CuisExperiment as a base to
automate the building of Cuis-Smalltalk distributions with
various combination of VM binary and image (32|64 bits). You
will have MacIntel, MacARM, Windows, LinuxIntel, LinuxArm,
LinuxRiscV associated with appropriate image and VM. Does not
Github offer service to automate packages built? I have just
migrated DrGeo repository to Github, I will take a look to that
(<a href="https://github.com/hilaire/drgeo" target="_blank">https://github.com/hilaire/drgeo</a>).<br>
</font></p>
<p><font size="4">Then you will have a set up that could scale more
easily to any additional needs like embedded system. And you
will be free to arrange the distribution in a way that fit the
host (Mac is a bit special)<br>
</font></p>
<p><font size="4">I feel it could also add visibility to
Cuis-Smalltalk to have these different distributions, it will
talk more specifically to the end user and will have a wow
effect. Compare all-in-one and LinuxIntel64 names. The later one
is crystal clear, not the former one.<br>
</font></p>
<p><font size="4">Regarding the current folder structure, I will try
to hide the complexity a bit more. I will have only two top
level folders. To illustrate, this is what a Linux user sees
when entering the DrGeo app folder:<br>
</font></p>
<p><font size="4">DrGeo<br>
├── ChangeLog<br>
├── DrGeo.sh<br>
├── License.txt<br>
├── README<br>
├── Resources<br>
├── transcript.txt<br>
└── VM<br>
<br>
</font></p>
<p><font size="4">Even the VM should not be visible to be honest. It
should be moved in the Resources folder.<br>
</font></p>
<p><font size="4">Nevertheless, all-in-one distribution will be
already an important progress and of course my opinion can be
completely discarded without harm.<br>
</font></p>
<p><font size="4">Have a nice day.<br>
</font></p>
<p><font size="4">Hilaire<br>
</font></p>
<div>Le 24/12/2023 à 13:28, Juan Vuletich
via Cuis-dev a écrit :<br>
</div>
<blockquote type="cite"><br>
The upcoming 6.1 release will be the first of a new series of
releases. We'll be doing a "stable release" that will later only
include critical fixes, every six months. This will be done in
addition to our usual rolling release, and it will follow the
RedHat Linux release process.
<br>
<br>
The stable releases are intended for:
<br>
- People who don't want to deal with constant updates and
breakage, and prefer to port their code to a new system from time
to time.
<br>
- Building End User Applications.
<br>
- Casual users, who just want to take a look at Cuis.
<br>
- People new to Smalltalk.
<br>
- Students who will be using Smalltalk for a semester.
<br>
<br>
For many of these use cases, I want to include only consistently
high quality code. So every package included needs to be currently
in use, tested, well maintained, etc. We'll need to work out a way
to deal with additional packages, from Cuis-Smalltalk-Dev repo,
other repos from Cuis-Smalltalk organization, and other repos
outside of it. This is just an initial version. It will grow.
<br>
<br>
Thanks,
</blockquote>
<pre cols="72">--
GNU Dr. Geo
<a href="http://gnu.org/s/dr-geo/" target="_blank">http://gnu.org/s/dr-geo/</a>
<a href="http://gnu-drgeo.blogspot.com/" target="_blank">http://gnu-drgeo.blogspot.com/</a></pre>
</div>
-- <br>
Cuis-dev mailing list<br>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><br>Nicolás Papagna</div>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><br>Nicolás Papagna</div></div>