Comment #3 on issue 1915 by renggli: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915
The monolithic ToolSet is indeed a big problem. I do not understand the proposed solution. I suggest that each of Browser, Debugger, Inspector, Transcript, Workspace, Process get their own AppRegistry subclass. There are already various (mostly unused) AppRegistry subclasses, splitting ToolSet into multiple classes would solve most of the problem.
An alternative (and probably even better) would be to make the standard tools unloadable, including their class extensions like Object>>#inspect, Object>>#browse, ... Like this the registry would not be necessary and people could just load whatever implementation they want (the menus are already configurable by other means).
Lukas
