Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Discussion 3 - Brandon Reynolds
Brandon Reynolds - gtg541q
The most useful feature of Squeak I've found is the basic System Browser. With it, you are able to view each and every aspect of the source code, modify it, and witness the changes you've implemented immediately. If there's something you don't understand, look up its class in the System Browser to better understand the method calls it uses, and the variables it instantiates. There is virtually no bounds to what you can learn about Squeak through the browser, as long as you have a basic understanding of what is happening.
The main drawback to such unprecedented access to the source code is that most often the code is poorly documented, making it difficult to follow. However, if you feel so ambitious, you may add your own comments to the source code, further assisting your understanding for later references. The System Browser is quite easily the most important feature of Squeak, and is accessed simply by bringing up the Halo over the object in question, then clicking on the little wrench icon on the right side and choosing "browse ... class". This will bring up the Hierarchy Browser (also useful), which you can then just click on the "Browse" button to pull up the System Browser. Enjoy the unlimited access to Squeak source, and best of luck interpreting it.
Discussion 3 - Jiasheng He This post had an extremely useful tool for Squeak. I often find myself juggling several system browsers in order to work on multiple functions, and cross-reference them. The Whisker Browser makes that process much simpler and more effective.
Discussion 3 - Stephen Ake I completely agree with this post, as it outlines the biggest shortcoming of Squeak: complete lack of appropriate and useful documentation. Although the code itself may be the documentation, unintuitive variable names or seemingly pointless redundancies in code make it frustrating to work with Squeak.
Links to this Page