Good ideas. Not silly if what you do is creating a gateway that gets stuff back from a REST api and you need to figure out some parts of what you get back (and one things is a huge Base64-encoded file - open that in the EyeTreeExplorer.) Now, on the GB thing, sure but the EyeTreeExplorer suddenly feels sluggish, not matter how much RAM there is. Phil On Thu, Mar 13, 2014 at 10:46 PM, Sven Van Caekenberghe <sven@stfx.eu>wrote:
But you have GB's of RAM, right ;-)
See EyeInspector>>#limit1 and limit2 that control how much to show in collections, maybe 100000 it too high ;-)
But in general, I think maybe we could use a dedicated EyeStringInspector.
I agree that viewing a bigger string in the explorer/tree view is a bit silly, but it is correct though.
Maybe #childrenFor[Object]: can be used to shortcut the depth of the tree. For strings characters could then no longer be shown.
On 13 Mar 2014, at 20:49, phil@highoctane.be wrote:
I see that you haven't clicked on a 17K long string that opens a 17K items long tree of characters with nice icons and makes your image bloat to 200+MB in size.
--> 223 162 288 bytes for XXXX.image
Look: (in 2.0 the explorer just shows a piece of text)
<13-03-14 20-47-35.png>
.
<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.ht... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.