Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Dicussion 3 - Michael Levy
This biggest problem that I've faced while working with Squeak is actually learning the langauge itself. Since Squeak itself is pretty poorly documented, it was very difficult to decipher the code and learn how to apply it, with a few changes as needed, to where I wanted to use it. An example of this is during a time where I was just trying different things in the workspace, I was trying to learn how to do just some pretty simple graphics in a morphic project and then animate those graphics. I was successful in getting the graphics loaded; however, I couldn't for the life of me get the animation to work. To solving this, I used the internet, in particular Google University (http://www.google.com/options/universities.html), and found code snippets with good documentation that I could then apply to my animation. In the end it turned out that I wasn't calling the right parent, startStepping, and my step method itself needed a little tweaking.
Discussion 3 - Andrew Calvin
I found this post to be useful b/c a lot of the features for SqueakPoint as well as just about any user interface, stems from event handling. I've toyed around with event handling in Squeak for a while with only a little success. This post helped give me some insight into how events are handled and can be manipulated in Squeak.
Discussion 3 - Stephen Rollyson
This post was helpful in that it gave me a way to follow the method hierarchy. A lot of what makes Squeak unique and useful is its inheritance; however, since Squeak is not documented very well, its hard to find where a particular method is to be used in another application. Withe the Message Finder tool, I can track down methods a lot easier.
Links to this Page