[squeak-dev] Re: Old menu items in TextEditors that currently
don't work
Tobias Pape
Das.Linux at gmx.de
Sun Mar 29 20:31:03 UTC 2015
On 29.03.2015, at 22:24, Levente Uzonyi <leves at elte.hu> wrote:
> On Sun, 29 Mar 2015, Tobias Pape wrote:
>
>>
>> On 29.03.2015, at 21:52, Stéphane Rollandin <lecteur at zogotounga.net> wrote:
>>
>>>> I consider explorer and inspector to be entirely different.
>>>> When I want to explore an object graph, I use the explorer.
>>>> When I want to directly manipulate a single object, or evaluate
>>>> expressions in its context, then I use an inspector.
>>
>> Just to chime in, I typically _exclusviely_ use the explorer, except
>> I have situations where the explorer is too slow (like really large arrays)
>> I really like having an overview.
>
> You can't evaluate expressions in the context of the object with an explorer. You can use #instVarAt: and #instVarAt:put:, but that's tedious.
… I just select them in the explorer and self is the selected object then.
Granted, I have to use accessors to change istvars, but well, typically this suffices.
> An object can hide its internals from the explorer (e.g.: Set/Dictionary).
Yes. but I'm mostly fine with this.
>
> Sometimes you don't care about other objects, just the one you're inspecting.
I didn't want to say the inspector is unnecessary but that I only use it in
special situations and the explorer 85% of the time.
Best
-Tobias
>
> Levente
>
>>
>> Best
>> -Tobias
>>
>>>> Based on my experience, these things rarely mix, which is probably why
>>>> these tools coexist.
>>>> It's probably possible to mix the two tools and get a usable result, but
>>>> please don't make the same mistake what the Pharo guys did.
>>>
>>> +1
>>>
>>> Stef
More information about the Squeak-dev
mailing list
|