<!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 Jaromir,<br> <br> But it will be essentially like that: Download the zip file, unpack, doubleClick on RunCuisOnWindows. bat.<br> <br> That's it.<br> <br> Thanks,<br> <br> On 12/25/2023 10:38 AM, Jaromir Matas via Cuis-dev wrote: <blockquote cite="mid:em682be79a-6e79-4038-9897-698ceddbe1fb@b96278a1.com" type="cite"> <style id="css_styles" type="text/css"></style> <div>Hi Hilaire, all,</div> <div><br> </div> <div>> <span style="font-size: 18px;">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.</span></div> <div><span style="font-size: 18px;"><br> </span></div> <div><span style="font-size: 18px;">Brilliantly put. For me that's <i>literally </i>it: download (the latest </span><span style="font-size: 18px;"><i>Windows </i>archive)</span><span style="font-size: 18px;">, unpack, doubleclick Squeak.exe, experiment, repeat.</span></div> <div><span style="font-size: 18px;"><br> </span></div> <div><span style="font-size: 18px;">(Maybe not the most effective workflow but i</span><span style="font-size: 18px;">n my case the simplest: I do not develop or deploy anything, just study the system and play</span><span style="font-size: 18px;">). </span></div> <div><span style="font-size: 18px;"><br> </span></div> <div><span style="font-size: 18px;">Many thanks,</span></div> <div><span style="font-size: 18px;">Jaromir</span></div> <div><br> </div> <div id="signature_old" style="clear: both;"> <div id="x57b63d33bbce4a9085be84e73df734d9"> <div>--</div> <div><font face="Segoe UI Light">Jaromir Matas</font></div> <div><font style="font-size: 10pt;" face="Segoe UI Light"><a class="moz-txt-link-abbreviated" href="mailto:mail@jaromir.net">mail@jaromir.net</a></font></div> <div><br> </div> </div> </div> <div><span style="font-size: 18px;"><br> </span></div> <div style="clear: both;"><br> </div> <div><br> </div> <div> <div>On 24-Dec-23 7:03:02 PM, "Hilaire Fernandes via Cuis-dev" <<a moz-do-not-send="true" href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:</div> </div> <div><br> </div> <div id="x8d818cd88c8b44e" style="color: rgb(0, 0, 0);"> <blockquote cite="2b14b1aa-55f6-4d80-9015-d647f72c8783@free.fr" type="cite" class="cite2"> <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 moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/hilaire/drgeo">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 class="moz-cite-prefix">Le 24/12/2023 à 13:28, Juan Vuletich via Cuis-dev a écrit : <br> </div> <blockquote type="cite" cite="mid:658823D9.2050006@cuis.st" class="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 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> </div> </blockquote> <br> <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>