<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi Hilaire, (inline) <div class="moz-cite-prefix">On 2026-07-22 11:10 AM, Hilaire Fernandes via Cuis-dev wrote: </div> <blockquote type="cite" cite="mid:4c4c0f06-7636-4231-8ed2-e70add304336@free.fr"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi, We need some explanation regarding the Cuis' directories. Some may be obvious, but there are questions. I suggest we discuss there, then I will compile as a Explanation documentation. Here are the directories found in the DirectoryEntry class side: ... Before proceeding with each one, I have a general question. How are managed these directories when constructing a bundle application (with DyboApp its top folder), which will likely reside outside of the Cuis-Smalltalk-dev directories structure? </blockquote> The main directory is #projectBaseDirectory. It is by default the parent of #cuisBaseDirectory and #userBaseDirectory. In your case it will be DyboApp #cuisBaseDirectory "The main folder with the directory structure where the files provided with Cuis reside. Usually will not contain user files. Following our install instructions in GitHub it is something like Cuis-Smalltalk/Cuis-Smalltalk-Dev In your case it would be DyboApp/Cuis-Smalltalk-Dev" #userBaseDirectory "The top directory for files generated by the system on behalf of the user Following our install instructions in GitHub it is something like Cuis-Smalltalk/Cuis-Smalltalk-Dev-UserFiles In your case it would be DyboApp/Cuis-Smalltalk-Dev-UserFiles" Some folders are usually not relevant to devs and apps. These are #smalltalkImageDirectory #vmDirectory #workingDirectory #currentDirectory and #roots. But the system must provide them to anyone who may need them. But the system is super flexible, and you can set up them the way you prefer. The only thing the system assumes is that #cuisBaseDirectory and #userBaseDirectory are set to reasonable places. You can set them in any way you prefer for Dybo. <blockquote type="cite" cite="mid:4c4c0f06-7636-4231-8ed2-e70add304336@free.fr"> For example, I observed that with a Cuis application, built on a subdirectory structure of Cuis-Smalltalk-Dev, its userPrefs.txt file (relative to userBaseDirectory) is saved in the Cuis-Smalltalk-Dev directory. </blockquote> userPrefs.txt is a user file generated by Cuis. By default it is created in the #userBaseDirectory, that is Cuis-Smalltalk/Cuis-Smalltalk-Dev-UserFiles <blockquote type="cite" cite="mid:4c4c0f06-7636-4231-8ed2-e70add304336@free.fr"> When I move this application bundle outside of the Cuis-Smalltalk-Dev, the userBaseDirectory is changed to the top folder of the Cuis application (here DyboApp/), the former userPrefs.txt is lost and a new one is created in DyboApp/ </blockquote> It shoudl go at whaever folder you set up for #userBaseDirectory. If your #userBaseDirectory is DyboApp/, then it will be created there. <blockquote type="cite" cite="mid:4c4c0f06-7636-4231-8ed2-e70add304336@free.fr"> I already document the -ud option at start-up. <a class="moz-txt-link-freetext" href="https://github.com/DrCuis/References-guides/blob/main/100-Host-Interactions/Command_Line_Options.md" moz-do-not-send="true">https://github.com/DrCuis/References-guides/blob/main/100-Host-Interactions/Command_Line_Options.md</a> Hilaire <pre class="moz-signature" cols="72">-- <a class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo" moz-do-not-send="true">http://mamot.fr/@drgeo</a></pre> </blockquote> Hope this helps. <pre class="moz-signature" cols="72">-- Juan Vuletich <a class="moz-txt-link-abbreviated" href="http://www.cuis.st">www.cuis.st</a> github.com/jvuletich researchgate.net/profile/Juan-Vuletich independent.academia.edu/JuanVuletich patents.justia.com/inventor/juan-manuel-vuletich</pre> </body> </html>