Ok, well let me comment about a few usablity issues. Explorer is a heavy weight inspection book, you have it, inspect and don't forget basicInspect. When working with objects that are subclassed off of ProtoObject like the objective-c class I ended up with dragging lots of methods from Object into the subclass to support Explore. Lastly when dealing with complex objects with twisty interconnects, like in a Sophie book structure Explorer would cheerfully be helpful and run off to visual show lots of things likely forever... requiring a cmd-interrupt to seize back control. Ensuring there is a way to do basic inspect would be helpful in rare cases then. On 3-Dec-08, at 8:26 PM, David Pennell wrote:
I agree.
Just to be clear - I use both because neither does all I need. Explorer is my default choice, but if I need to look at the innards of a String, I launch an Inspector. It seems like it would be easy enough to fix these in Explorer and then make that the default inspector.
I'm just returning to Squeak after 8 years and wondering if there are other reasons folks use Inspector instead of Explorer.
-david
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================