One of the tasks we should do is to save our image. I recommend using the World menu and selecting "previous project" until you get back to your main personal project. In my case that would be the project named "sbw".

Execute a "save" from the World menu.

We saw a place during this development exercise where work was left "incomplete".
The capability of copying a file from a local system to a remote system could be added.

The ChangeSet for the source contained in this example can be downloaded from my web site. I recommend you follow the example and manually type the code as a better way to learn. However, you are welcome to use the change set here if you are concerned about typos or mistakes.

I hope this was an enjoyable excursion for you. It may have seemed pretty choppy at points, and it's a bit odd to take someone else through setting up a development environment look-and-feel to one's personal taste. But, it's how I work while in Squeak.

While typing these pages into HTML documents I was constantly rethinking how I had the pages laid out and in what order the material should be presented. But those were also distractions that just kept me from getting something written down and hopefully usefull.

It may be worth noting that this entire HTML document was produced inside Squeak itself. I wrote a little code to capture parts of the screen as JPG files (the built-in method in Squeak produces GIFs) but actually used FileList to edit all of the documents as I worked. Also, I never really used a PC to do the Windows stuff. I did use Windows 98 for the example, but I actually ran Windows 98 from VirtualPC on my Macintosh PowerBook G4 running OS X. So I never really left the Mac environment while writing the Squeak 3.5 version of this tutorial.

Please write to me via e-mail if you have constructive feedback to share.
Stephan B. Wessels

Back to the beginning of this example.
Back to the main tutorial page.