I recently setup a second computer for Squeak development work. I'd been using an Apple Macintosh PowerBook G4 running OS X. I also had an older Compaq desktop computer, that used to run Windows 98, sitting idle. I wanted to use it on a small LAN and investigate some ideas in networked Squeak development. The actual networked Squeak research is not what is documented here. Instead, this document details the steps during setup and some small code work to make it easier for me to move Squeak source files between machines.
The first thing I did was format the PC and install Mandrake Linux. I really wanted a Unix based platform behind both Squeak development environments. After the Linux box was connected to the LAN and ready to use, and after installing Squeak 3.2 for Linux, the development project began.
Steps taken, and why, are described here. Hopefully some interesting work and design habits will surface in this example that may help others as they develop using Squeak.
The activities included in this example include:
· Modify the appearance of the Squeak environment using standard menus.
· Use FileList to examine files on a remote FTP server we define.
· Write code to extend a basic capability of FileList
· Use SUnit to test code we have written and will write
· Write more extensive code to add another new feature to FileList
Proceed linearly through this example. You may skip over environment/setup sections that relate to personal colors and styles. These areas are noted throughout the document.
Topics:
Setup of the Squeak 3.2 environment (OPTIONAL)
Change Sets and Projects
Using Squeak's FileList tool to copy files from another networked computer
A first enhancement to FileList. Copy just the file name
Writing SUnit to test our code
A second enhancement to FileList. Copy the file from either a local directory or a remote computer
Unfinished work to consider
Back to the main tutorial page.