Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Discussion 3 - Laura Parker
My initial problem with Squeak was not knowing where on earth I was supposed to actually write my code. The workspace looked promising, since it was blank, but then I did not know how to give classes names and make them interact. The System Browser looked a bit terrifying because there was all this other code in there and the last thing I wanted to do was break that, and then not know how to fix it. The solution to this problem was just a little bit of bravery and trying things out. I had to download a few new copies of Squeak before I figured out I needed to put my classes in the System Broswer and then I could test my code in the Workspace.
The most frustrating thing for me to overcome in Squeak so far has been not being able to click back and forth between methods I am in the process of writing if they are unsaved. I am used to being able to writing code that needs a function to complete it and then writing that function. You can't do this in Squeak because you cannot go to a different method if your current one is not saved and your current method will nto save if it has an undefined method name in it. My first solution was to erase anything that prohibited the method from being saved and then proceeding as I was supposed to in the first place. I also sometimes just commented out the offensive lines. Then one day it dawned on me, I can just have multiple System Browsers open at the same time. That way, I can look at other methods by just switching between browsers. It creates a little bit of clutter on the screen, but it's the best solution I've found so far.
Links to this Page