<!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> 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: cuisBaseDirectory currentDirectory projectDirectory userBaseDirectory coreUpdateDirectory packageDirectorry trueTypeFontsDirectory fileOutsDirectory logsDirectory newPackageDirectory savedChangeSetsDirectory userChangesDirectory userDirectory: roots smalltalkImageDirectory vmDirectory workingDirectory 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? 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. 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/ 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">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">http://mamot.fr/@drgeo</a></pre> </body> </html>