These are my two strange ways of managing code I care about -
* Send it to the list. Go to the Chage List, and instead of file out, do
"mail to the list". It's an interesting storage medium - it's
distributed, has multiple access paths (all messages with subject
prefixed [ENH], [Goodie] or [Fix] are picked up and stored on a special
page, for example), is backed up, searchable, and sometimes people
benefit by it. Of course this requires at least some potential
usefulness for whatever it is...
* I maintain the Squeak port of the Refactoring Browser, which is made
of several packages, and lots of code that should be accessible for
people to download. SCAN is a very nice repository I use by Hans-Martin
Mosner. You can start by browsing -
http://squeak.heeg.de:8080/Squeak/Packages/Refactoring%20Browser/Squeak%
20RB
It has a nice Squeak client too. You can keep some/all of your code
private to your machine, or post it to the server, as you wish. I like
it much.

Daniel

Chris Muller <afunkyobject at yahoo.com> wrote:
> 
> --Boundary_(ID_JkDIDEoWPYmxThDgYh5gzA)
> Content-type: text/plain; charset=us-ascii
> Content-transfer-encoding: 7BIT
> 
> 
> I am a fascinated Squeak-newbie bursting with questions.  I have lots of Smalltalk experience, but in other dialects (VA & VW).  I'm finally ready for Squeak, but am still trying to get familiarized with my new environment.  I have a couple of questions.
> 
> - What are some best-practices for maintaining my code in a safe-as-ENVY way.  If I'm writing new code every day that I do not want to lose, is it reliable enough to simply back up my changes file every day?  Or do I need to file-out all of my ChangeSets for a more reliable recovery should the need arise.  I imagined there would be some sort of automatic recovery script that would re-apply all changes in the changes file after the timestamp of the image save, similar to the "Make Image Consistent" command in an Envy-based environment.  I noticed a couple of interesting methods:
>