I believe that understanding a program by by reading its code 
statically instead of stepping through it with the debugger
is like understanding a movie by reading its script instead of watching 
it.  ;-)

So also look at the tests and parameterless methods of the class side 
(typical example*-methods) if there are any.
They will set up the right context to run specific methods.
Then you can put a halt somewhere and step through the code with the 
debugger.

Browsing references to classes via alt-n on the class selected also 
helps me to understand the coarse layout of an unknown system.

Cheers,

Markus

p.s. I am working on making the connection between methods and tests 
explicit, so that the tests would show up directly besides their tested 
methods.

http://www.iam.unibe.ch/~gaelli/oneMethodCommands.png
http://www.iam.unibe.ch/~gaelli/oneMethodExampleBrowser.png
http://www.iam.unibe.ch/~gaelli/UnitTestTaxonomy.pdf

On May 31, 2005, at 16:47, Daniel Vainsencher wrote:

> If you are willing to spend effort understanding a relatively new and 
> raw tool, Mudpie might help. You choose a set of categories, it shows 
> you which are dependent on which (in a diagram, using Ned's 
> Connectors). This gives you quite a bit of information on the 
> structure of the code. Obviously this is just one aspect of 
> understanding code, but I find it helps to navigate.
>
> Install and find links to more info on SqueakMap.
>
> Daniel
>
> Chris Schreiner wrote:
>>> On 31-May-05, at PM 06:05, Chris Schreiner wrote:
>>>
>>>>  Hi
>>>>
>>>>  There is a thing in the Java world, which I am certain some of you 
>>>> have encountered, it can be found at http://www.javaalmanac.com. 
>>>> Its just a crude lookup mechanism, using simple keywords to 
>>>> identify example-code-segments.
>>>>
>>>>  I was wondering if any of you know of a similar service for 
>>>> Squeak. If there is none, I guess it would be of interest to the 
>>>> Squeak community to have such a thing.
>>>
>>>
>>>
>>> Emm.. Browse for implementers/senders/references, etc or use the 
>>> method finder?
>>>
>> I guess you're right, however, I cannot see how I can effectively 
>> learn about the framework as a whole coherent system (if it is). 
>> Browsing specific areas suggest that I already know about the 
>> existence of those areas. Of course, there are plenty of techniques I 
>> don't know about, so feed me please, but I do think I have the basic 
>> understanding how to use the search/browse facilities in Squeak.
>> So my point is, I guess, is there a facility related to Squeak that 
>> allow me to understand the framework as a whole?
>