It would be great if we could reach an effective goal: having a super cool inspector and avoiding reinventing all this.
GTInspector is truly effective and usable. Maybe we should change the name of the moose image into Pharo-Dev or something. Alexandre On Mar 13, 2014, at 8:51 AM, Sean P. DeNigris <s...@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. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
