Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
When coding the LinkToAPageButton for milestone 2, I had the problem of trying to get the button to link to an actual page instead of just being able to link to a page number. The link would work just fine unless you rearranged the order of the pages, which was a requirement of the link's functionality. I found BookMorph's goToPage:morph function, but I didn't know how to get the morph for the page that I wanted to link to. I was able to overcome this problem by viewing the code in BookMorph for the goToPage:number method. I was able to see how this code was finding the actual morph for the page number, and use a similar version of this code to have the link go to the actual page, instead of just a page number. This is a good example of how squeak's ability to view its own source code helps you in tackling other problems.
I found Mark Shalda's explanation of the hierarchy browser to be incredibly useful. Before I knew about this if I wanted to find where a method in a class came from in its hierarchy I would simply look at the class definition to see what it was a subclass of, and repeat this process tracing up the tree until I found the method I was looking for. This was obviously quite tedious, and the use of the hierarchy browser greatly simplifies this.
I also found Andrew Calvin's description of event handling to be very helpful. So far I have only used the mouseDown event, but after reading his overview I can see how all the different events Squeak handles can be very useful and will come in quite handy for the completion of the SqueakPoint project.
Links to this Page