I went back to compare the explorer in 2.0, the only visible (not behaviour) difference that I see is the class field, it would probably be better to lose that:

<Screen Shot 2014-03-13 at 20.28.45.png>

<Screen Shot 2014-03-13 at 20.29.10.png>

But I hate the 'all inst vars' field, who uses that and for what ??

On 13 Mar 2014, at 20:16, phil@highoctane.be wrote:

I agree with that.

I was inspecting a ZnResponse yesterday and it was very hard to see the contents etc.

A general pain. I was clicking on the "inspect" option to see what the real content was. I was cursing a lot.

Phil

 



On Thu, Mar 13, 2014 at 12:51 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
I'm glad we're re-inventing the tools! And, I'm struggling with this tool in
its current form...

As others have mentioned, the "class" pseudo-variable is confusing, but here
are some that I find worse:
- The receiver does not change with the selection. For me, this was a key
feature of the explorer.
- It does not properly update e.g. if you are inspecting a class containing
a dictionary and add an item to the dictionary, collapsing and expanding the
dictionary node does not show the added item. It seems you must open an
entirely new inspector.
- If you toggle from EyeTreeInspector to EyeInspector, your code in the
bottom pane is lost



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.