Some tips people have given me:

• Ralph Johnson: "Images are fragile." Don't count on your image. File things out. (You can write out the text, a fileout, of a class or a category by using the middle-button menu from the System Browser. You can fileIn from the File List.
• Also from Ralph: Use Projects. Create a New Project (from the middle-button down menu on any part of the background), then "Enter" (button-down in project window) the project. Any changes you make inside the project can be filedOut as a single file.
• Adele Goldberg: "Make build scripts." Build scripts that fileIn all your code in the order that you want it filedIn. (FileStream fileNamed: 'CashDevice.st') fileIn will fileIn a file for you.
• Watching Dan and John set up for OOPSLA: From the File List (Middle-button menu on background, choose "Open", then "Open File List")

  Tips gleaned from the Mailing List:

  • Relation between sources, image, changes, and VM (see Where is the sources file? Why do all my methods have variables t1, t2, etc.?)
  • When to use separate images for separate projects (see How do you store your code in Squeak?)
  • Loading and reloading code (see What's a ChangeSorter for?)
  • Using projects and change sets (see How do you store your code in Squeak?)

  ---

  "More About Squeak..."
  Home Page for How To Squeak

  Last modified at 1/30/98; 9:41:56 AM
  Other Links of Interest
  College of Computing | EduTech Institute | GVU Center
  Mark Guzdial | CS2390, Modeling and Design | STABLE