<!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, On 5/25/2025 5:14 AM, Hilaire Fernandes via Cuis-dev wrote: <blockquote cite="mid:394ad481-aa19-40ee-8a14-480db9a81e3a@free.fr" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hi Juan, Answers in-lined. <div class="moz-cite-prefix">Le 19/05/2025 à 20:25, Juan Vuletich a écrit : </div> <blockquote type="cite" cite="mid:682B77AE.3030607@cuis.st">"How-to guides" also makes a lot of sense. However I would completely remove the "Virtual Machine" section. Cuis-Smalltalk-Dev already includes VMs for major platforms. 99% of Cuis users don't need to build a VM. Helping the other 1% is fine, but I think that is "Pro Level" documentation and it belongs somewhere else. Having that in the same place as building packages or working with layouts may make people think that hacking the VM is as important or frequent as doing packages and layouts. Even worse. It may lead people to believe that building their own package or using Layouts in their code is as difficult and "experts only" as hacking the VM. We provide well tested VMs for most platforms so people can forget about this as much as possible. </blockquote> Noted, I agree under the "first impression count" perspective. It may give an unjustified feeling of difficulty. I just removed it. </blockquote> Thanks. <blockquote cite="mid:394ad481-aa19-40ee-8a14-480db9a81e3a@free.fr" type="cite"> <blockquote type="cite" cite="mid:682B77AE.3030607@cuis.st"> "Reference guides" is OK. I think that other reference material could be added here. Perhaps the services offered by MorphicCanvas would belong here. Or some comprehensive discussion about Unicode. I'm sure there are many more that don't come to my mind right now. "Explanations" looks like a place to put stuff that didn't belong in any of the previous categories. Currently it includes both introductory material, highly technical stuff, and lose bits of information. I think this could be improved. For instance, separating "Philosophical" and "Technical" material as done in Cuis-Smalltalk-Dev/Documentation, makes sense to me. </blockquote> The idea is to have deeper understanding, in both a technical perspective (it may relate to the Technique repo) and more large scale perspective (aka philosophical). The latter one may be the one not fitting this category as described in the documentation system, but we are free to diverge. <blockquote type="cite" cite="mid:682B77AE.3030607@cuis.st"> Additionally, the question remains whether this should duplicate the material in Cuis-Smalltalk-Dev/Documentation, or which parts belong in DrCuis, and witch belong in Cuis-Smalltalk-Dev.</blockquote> Duplication may result in wasted resources. </blockquote> Agreed <blockquote cite="mid:394ad481-aa19-40ee-8a14-480db9a81e3a@free.fr" type="cite"> Options: keeping VM, plugin, FFI to Cuis-Smalltalk-Dev, and other more classic user at DrCuis </blockquote> Yes. This is a good idea. As a start, I just removed Documentation/Technical/Morphic as it was moved to DrCuis. Same for Documentation/Technical/MiscProgramming and Documentation/Technical/Compiler. <blockquote cite="mid:394ad481-aa19-40ee-8a14-480db9a81e3a@free.fr" type="cite"> <pre class="moz-signature" cols="72">-- <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo">http://mamot.fr/@drgeo</a></pre> </blockquote> Thanks, <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>