Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Discussion 3 - Cooper Welch
1. Call me an idiot, but the morphic graphic system in Squeak was a rather steep learning curve for me. Up until my experience with Squeak, I hadn’t ever dealt with an object-oriented language where gui objects could be “embedded into” each other to create greater gui units. All the programming languages I’ve used have simply had pre-made gui objects (such as text labels and buttons) that one just slaps into the program and attaches code to (such as action listeners). The whole idea surrounding how morphic structures can be manipulated and combined was incredibly abstract and took me a while to get used to. To remedy the problem I simply stumbled through code, googled, and read various text materials until I thoroughly understood the concept. Needless to say, it was somewhat difficult at times due to the scarce amount of Squeak documentation available.
2. I consider the browser in Squeak to be incredibly useful. It provides an excellent means for code organization and look-up. For example, if I wanted to see what BookMorph’s code looked like, I could simply open up a browser and search for the BookMorph class. Additionally, the ability to click on a morphic object and instantaneously open up a browser to look through its class hierarchy provides a wonderfully systematic and understandable way of seeing its underlying code structure.
1. Jonathan Reitnauer's discussion was extremely helpful for me. Up until reading his post, I had no idea how to add pages to a Bookmorph.
2. Hai Phan's discussion provided me with an understanding of how string equality works in Squeak.
Links to this Page