> There where two systems in parallel for making the browser pluggable. I > removed one months ago > so we have just one. > > It was really a mess: some caller uses “Smalltalk tools browser”, others > “SystemBrowser default” > (subclass of AppRegistry). > > This was quite complex and everything was duplicated, and everything mixed > together. > (Smalltalk tools browser returned SystemBrowser default). > > In short: a mess. It tool quite some effort to clean up. > > Now the “Smalltalk tools browser” (ToolRegistry) is not perfect. > > -> it should provide a way to register multiple implementations for the > same tool > -> it should provide a Settings interface to switch between the tools > -> it maybe should use pragmas instead of the current scheme > > Yes, unifying everything to us ToolRegistry instead of AppRegistry meant we > lost the menu > entry… but now we have *one* mechanism, not two incompatible ones.
yes but the menu was handy. Next time ask and I will just call the right behavior from it.
