On Aug 1, 2011, at 12:24 PM, Randal L. Schwartz wrote:
"Stéphane" == Stéphane Ducasse <stephane.ducasse@inria.fr> writes:
Stéphane> may be :)
Stéphane> but for me this flat view never worked.
As an example of how it was useful to me... the WABrush classes are fairly deep, particularly in the form elements, and it was difficult to see how to configure a given brush. Flattening it as a protocol browser instantly gave me the full API, including letting me know which methods were inherited so are also likely to be used by other common brushes.
The hierarchy browser can do *some* of that, but I find them both to be useful at different times.
Agreed 100%. Heirarchy browser is decent at figuring out what messages an object responds to, great for figuring out where exactly those are implemented. But if I want to know all the messages it responds to, protocol browser is critical. Pat