[Setools] Code graphs, and Exploring browser

[Herbert König]

Hello Balázs,


BK> When i try to understand some aspect of the code, i usually end up with lots of
BK> browsers (and explorers, inspectors, workspaces, pointerfinders,
BK> debuggers, ...),
you should try TracingMessagesBrowser from SqueakMap which helps
against the proliferation of Browsers when using senders and
inplementors.

It gives an indented list of the static control flow above the code
pane.

BK> as a semi-manual process, resembling BabySRE's collaboration diagram, but more
BK> specific to smalltalk and more focused on code, more elaborate, and
BK> somewhat more
BK> automatic.I decided not to go into details. Please tell me about your
BK> impressions.
For a time I used BabySRE but with more complex projects screenspace
was a limit. And it was too slow on my old computer then.

If it would be able to show even more aspects, the diagrams would
become even bigger. And more complex, so how to route all the
connectors. Scrolling (virtual screen) and nesting might help, but I
believe it's fragmenting the graph and thus hinders understanding.

From my experience in CAD you need a big visual representation which
the srceen can't deliver. People make A0 plots, sketch changes by Hand,
change in the computer, plot again.


Cheers,

Herbert                            mailto:herbertkoenig at gmx.net