<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> For daily code session, I have in mind the workflow Juan suggests: 1. Load your work-in-progress package in Cuis 2. Write code 3. Save your package 4. Repeat at 2. 5. Commit your package to whatever CVS you prefere Never save the image! Start every code session with a fresh image! May be a step "0. Setup your image with browser and workspace content" can be prepended. The book could suggest some scripts to automate several setup scenarios. (browser, workspace, workspace content, font, etc.) As the target audience of the book is neophytes to Cuis-Smalltalk, getting it right at the first place is of some importance. Take care Hilaire <div class="moz-cite-prefix">Le 09/11/2020 à 21:44, Philip Bernhart via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:87r1p2jm5p.fsf@posteo.de"> <div class="moz-text-plain" wrap="true" graphical-quote="true" style="font-size: 16px;" lang="x-western"> <pre class="moz-quote-pre" wrap="">Hi, "ken.dickey--- via Cuis-dev" <a class="moz-txt-link-rfc2396E" href="mailto:cuis-dev@lists.cuis.st" moz-do-not-send="true"><cuis-dev@lists.cuis.st></a> writes: </pre> <blockquote type="cite" style="color: #999999;"> <pre class="moz-quote-pre" wrap="">On 2020-11-09 05:17, H. Fernandes via Cuis-dev wrote: .. </pre> <blockquote type="cite" style="color: #999999;"> <pre class="moz-quote-pre" wrap="">* Code Management, not sure yet it is worth writing this chapter. My basic use is very basic, .. </pre> </blockquote> <pre class="moz-quote-pre" wrap="">I was thinking that we should stress the _personal_ part of personal software. With Cuis, it is harder to lose your work. </pre> </blockquote> <pre class="moz-quote-pre" wrap="">Well, I must admit that I never have seen the "it's harder to lose your work" part. For me it was the opposite. It's in my opinion easier to lose the work. Sure in theory the changeset was written to disk, but then accurately bringing the image in a state as it was before the crash is hard. But maybe I haven't got a mail or something. Normally I resorted to pressing save image regularly as it's easier to store the current state. So when people write that chapter, showing the worst-case recovery issues would be the more useful contributions. My 0.02 EUR, Philip <div class="moz-txt-sig">-- Cuis-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Cuis-dev@lists.cuis.st" moz-do-not-send="true">Cuis-dev@lists.cuis.st</a> <a class="moz-txt-link-freetext" href="https://lists.cuis.st/mailman/listinfo/cuis-dev" moz-do-not-send="true">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </div></pre> </div> </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="https://pouet.chapril.org/@hilaire">https://pouet.chapril.org/@hilaire</a></pre> </body> </html>