Hi,
I think the inspector should become more prominent in the life of a Pharo developer.
For example, the Inspector is perhaps the last tool you might see as useful for code manipulation, but if you see code as objects, it makes perfect sense to have some support in the inspector.
To show how it can be different, I described two recent scenarios in which the GTInspector was essentially the only tool readily available to support editing of a custom set of methods:
http://www.humane-assessment.com/blog/guiding-custom-changes-with-gtinspector
I would be happy to hear any feedback.
Cheers,
Doru
--
"Every thing has its own flow"