[Cuis-dev] Getting Started instructions directory structure

[Nicola Mingotti]

hi Bernhard,

I add my 2 cents experience. This is the way i found to keep things 
organized.

for each cuis program i want to write, i mean a program i want to use on 
the long run i do:
1. $> mkdir cuis-project-foo1
2. $> cd cuis-project-foo1
3. $> put the VM tar file here and uncompress it here
4. $> git clone Cuis-Smalltalk-Dev

*] disadvantage: it will take space on your disk and i will not be in 
sync with Cuis evolution.

*] advantage. You can be sure your program will be always working once 
the test phase is over.

Then, I keep a directory 'cuis-project' whithout a project name. There 
is where i test
stuff, upgrade Cuis quite often. I work in 'cuis-project' most of the time.

bye
Nicola







On 12/22/21 11:42, Bernhard Pieber via Cuis-dev wrote:
> Hi Juan,
>
> Thanks for the clarification. Makes sense.
>
> Cheers,
> Bernhard
>
>> Am 21.12.2021 um 16:51 schrieb Juan Vuletich via Cuis-dev <cuis-dev at lists.cuis.st>:
>>
>> Hi Bernhard,
>>
>> On 12/21/2021 5:53 AM, Bernhard Pieber via Cuis-dev wrote:
>>> Hi Juan,
>>>
>>> Thank you for the fast response. Now the shell scripts work as intended.
>>>
>>> One thing I am still unsure about: Where do you put the VM and where the working images, in MyProject or in Cuis-Smalltalk-Dev? If in Cuis-Smalltalk-Dev the Git repository gets dirty because of various files that get created, e.g. ThePig.txt.
>> I put the VM at MyProject, and sometimes save images in
>> Cuis-Smalltalk-Dev. I don't have a defined process for removing unneeded
>> files. Maybe a couple of additional shell scripts could be of use.
>>
>>> I guess the project specific packages would go into a subdirectory of MyProject like Cuis-Smalltalk-MyProject, which would be a Git repository, right?
>> Yes. That is the best way to keep them organized.
>>
>>> If you work on different projects, would you clone all package repositories for each of them?
>> This is matter of personal preference. I usually use a single main
>> folder. But if I was maintaining an end user application, I'd give it
>> its own Cuis setup, to do updates to Cuis only when I'm willing to fix
>> any possible breaking.
>>
>>> Cheers,
>>> Bernhard
>> Cheers,
>>
>> --
>> Juan Vuletich
>> www.cuis-smalltalk.org
>> https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
>> https://github.com/jvuletich
>> https://www.researchgate.net/profile/Juan-Vuletich
>> https://www.linkedin.com/in/juan-vuletich-75611b3
>> https://independent.academia.edu/JuanVuletich
>> @JuanVuletich
>>
>> --
>> Cuis-dev mailing list
>> Cuis-dev at lists.cuis.st
>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>