Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Discussion 3 - Jonathan Reitnauer
One problem that I experienced while programming in Squeak was trying to figure out the structure of how different layout elements were used on a page in a BookMorph. There are PasteUpMorphs which are the pages in a BookMorph and on those can be placed TextMorphs, SketchMorphs and any other kinds of morphs that make up the page elements. A good way I found to visualize the code layout for all of this is to use the Explore feature.
If you bring up a halo on an object and then click the debug button and select “Explore Morph” you will get a window that contains the class representing that object at the top root level with a sideways pointing arrow. Then you can click the arrow to open a view that shows all of the variables and submorphs that are contained in that object. All other objects also have their own arrows so you can see a nested view of what contains what. This allowed me to see how BookMorphs were constructed and what types of objects should be put where.
One particular feature of Squeak I have found useful is the ability to easily view the code for any screen object through the “Browse Morph Class” feature. This can also be evoked from the debug menu. This can be very helpful for example, if you want to duplicate or modify the functionality of some widget. By looking at what it does as an active screen object and then quickly jumping to the relevant code sections, it can be determined relatively quickly how it is working and what parts of the code are performing which features.
Links to this Page