How does a newbie get past the feeling thay he is trying to understand an elephant whilst looking through a keyhole?

Antony Blakey antony.blakey at
Thu May 4 13:37:57 UTC 2006

All of which reinforces the original point of the thread. So many things definitely don't "just work" - especially given 
that I had no idea if this was a) known to be broken; or b) my config error; or c) broken in my particular version; or 
d) fixable by investigating the code.

Not a criticism, just an observation that it's difficult to empathise with a newbie when you are not.

As an aside, I guess this is a significant advantage that e.g. VW has over Squeak.

Chris Muller wrote:
> Yes it works fine with Refactoring browser, it just doesn't get called because Refactoring Browser modifies methods which call the standard methods browser to call its own VERY unfriendly methods browser.
>  This might be avoidable if you load Tracing Messages Browser AFTER Refactoring browser, otherwise you'll have to revert a few methods that Refactoring Browser installs which calls its own terrible methods browser.
>  If you are a new Smalltalker, this would be a good exercise in finding and updating code to suit you.  You can find the methods which need to be changed by using the Command+Shift+e on the text of the menu (i.e., "implementors of...").
>  To get you started, #implementorsOfIt and #sendersOfIt in ParagraphEditor will take care of the ones when browsing out of a code pane..  Another is CodeHolder>>#messageListKey:from: which will take care of using the hot key invocations from message lists..
>  This is life in Smalltalk.  The system is open so things sometimes get changed, particularly when it comes to the IDE.  Thankfully, the system is open so at least you can take control of your own software destiny.
>   - Chris

More information about the Squeak-dev mailing list