My 1.1 image is showing its age, not because it is aging but because Pharo is evolving. The last time I had to give any thought to it (and I am not a fan of the new inspector), I found that activating the standard toolset gave me most of what I wanted, including using the ordinary inspector instead of the new inspector. However, I just looked at the code I use (aka Migrate) to check, save and load packages, and find that ToolSet default:StandardToolSet. is commented out. It is not immediately obvious whether the image I am using now was built that way, or if (as sometimes happens) I tried a new image, noted that the change was no longer needed and made the change for "next time." If there is a way to keep the new inspector and make it easy to disable, then by all means keep it around. I happen to greatly prefer the explorer for what the new inspector tries to do, but if it is dormant, what's the harm? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck@gmail.com] Sent: Thursday, September 16, 2010 9:26 AM To: Pharo Development Subject: [Pharo-project] Enable/Disable NewInspector Hi, is there a way to enable and disable NewInspector in a PharoDev image? I don't want to remove neither not load. I want that having both in the system, if there is a way right now to decide which one to use. thanks mariano