On Wed, Oct 29, 2008 at 04:20:55AM +0200, Igor Stasenko wrote:
I'm implemented a new ToolRegistry class, which can work as replacement of ToolSet.
It would require a 'bit' refactoring, to replace all references to 'ToolSet' with 'Smalltalk tools'.
What i discovered during implementation, if we migrate to new class, a lot of stuff can be cleaned up. For instance,
Smalltalk tools inspectorTypes
holds a dictionary of Class name -> inspector class name so, one could simply register own inspector by including a line:
Smalltalk tools inspectorTypes at: #MySpecialClass put: #MySpecialInspector
in package/class initialization method, instead of overriding #inspect method.
Actually, you are supposed to override inspectorClass, but yes, that does sound more uniform. Does it support inheritance, so that subclasses of MySpecialClass will use the nice inspector too? I don't see anything wrong with inspectorClass, except for the fact that ObjectExplorer and Inspector don't share the same inspection model, which means you see different things when exploring vs inspecting a CompiledMethod -- Matthew Fulmer -- http://mtfulmer.wordpress.com/