Smalltalk › Pharo › Pharo Smalltalk Users

Playground inspector and the self variable

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

Esteban A. Maringolo

Playground inspector and the self variable

Is it okay that the Playground's inspector drills down on the self
variable indefinitely?

It is... #(1 2 3) "Do it and go" will result in an Array being
inspected, if I click on "self" it will open a new inspector on the
side on the same object, and this can as deep as you want.

I would block that from happening, in the raw tab, the "self" variable
shouldn't drill down, sometimes I just want to select it to run an
expression where self refers to the inspected object.

Does it make sense what I propose? Or is there any use case where
drilling down recursively ad infinutum is useful?

Regards!

Esteban A. Maringolo

Tudor Girba-2

Re: Playground inspector and the self variable

Hi,

Indeed, this part of the inspector will be revisited for Pharo 5.

But, what exactly do you mean by " I just want to select it to run an expression where self refers to the inspected object"?

Cheers,

Doru

On Fri, May 29, 2015 at 5:30 PM, Esteban A. Maringolo <[hidden email]> wrote:

Is it okay that the Playground's inspector drills down on the self
variable indefinitely?

It is... #(1 2 3) "Do it and go" will result in an Array being
inspected, if I click on "self" it will open a new inspector on the
side on the same object, and this can as deep as you want.

I would block that from happening, in the raw tab, the "self" variable
shouldn't drill down, sometimes I just want to select it to run an
expression where self refers to the inspected object.

Does it make sense what I propose? Or is there any use case where
drilling down recursively ad infinutum is useful?

Regards!

Esteban A. Maringolo

www.tudorgirba.com

"Every thing has its own flow"

Esteban A. Maringolo

Re: Playground inspector and the self variable

2015-05-29 12:36 GMT-03:00 Tudor Girba <[hidden email]>:
> Hi,
>
> Indeed, this part of the inspector will be revisited for Pharo 5.

Good. I'm sure this can be backported easily ;)

> But, what exactly do you mean by " I just want to select it to run an
> expression where self refers to the inspected object"?

I have the strong habit of running expressions (it is, send messages)
to objects directly in the inspector, in the case of the example
array, I can fiddle selecting the different elements in the array and
finally select the array itself ("self") to select as the receiver. I
expect to write these expression on the pane of the right, even when I
could do it on the pane of the left.

I hope I explained myself. :)

Esteban A. Maringolo

Esteban A. Maringolo

Re: Playground inspector and the self variable

Also... I find myself accidentally closing the whole Playground in an
attempt to just close the inspector.

I know this is related with me not being the smartest guy in the
block, but I'm so used to discard inspectors, and when you're somehow
deep inspecting you completely forgot you started in a "workspace".

Esteban A. Maringolo

2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <[hidden email]>:

> 2015-05-29 12:36 GMT-03:00 Tudor Girba <[hidden email]>:
>> Hi,
>>
>> Indeed, this part of the inspector will be revisited for Pharo 5.
>
> Good. I'm sure this can be backported easily ;)
>
>> But, what exactly do you mean by " I just want to select it to run an
>> expression where self refers to the inspected object"?
>
> I have the strong habit of running expressions (it is, send messages)
> to objects directly in the inspector, in the case of the example
> array, I can fiddle selecting the different elements in the array and
> finally select the array itself ("self") to select as the receiver. I
> expect to write these expression on the pane of the right, even when I
> could do it on the pane of the left.
>
> I hope I explained myself. :)
>
>
> Esteban A. Maringolo

Tudor Girba-2

Re: Playground inspector and the self variable

In reply to this post by Esteban A. Maringolo

Hi Esteban,

On Fri, May 29, 2015 at 5:42 PM, Esteban A. Maringolo <[hidden email]> wrote:

2015-05-29 12:36 GMT-03:00 Tudor Girba <[hidden email]>:
> Hi,
>
> Indeed, this part of the inspector will be revisited for Pharo 5.

Good. I'm sure this can be backported easily ;)

It won't because this will be a new implementation :).

> But, what exactly do you mean by " I just want to select it to run an
> expression where self refers to the inspected object"?

I have the strong habit of running expressions (it is, send messages)
to objects directly in the inspector, in the case of the example
array, I can fiddle selecting the different elements in the array and
finally select the array itself ("self") to select as the receiver. I
expect to write these expression on the pane of the right, even when I
could do it on the pane of the left.

I hope I explained myself. :)

I still do not quite understand where the problem is.

Could you give me a step by step description?

Cheers,

Doru

Esteban A. Maringolo

www.tudorgirba.com

"Every thing has its own flow"

Tudor Girba-2

Re: Playground inspector and the self variable

In reply to this post by Esteban A. Maringolo

Hi,

Indeed, this is a usability issue.

However, your code is not lost. You can find the playground easily, and if you inspect the same objects, the raw presentation will show you the last entered code for each class.

Cheers,

Doru

On Fri, May 29, 2015 at 6:15 PM, Esteban A. Maringolo <[hidden email]> wrote:

Also... I find myself accidentally closing the whole Playground in an
attempt to just close the inspector.

I know this is related with me not being the smartest guy in the
block, but I'm so used to discard inspectors, and when you're somehow
deep inspecting you completely forgot you started in a "workspace".

Esteban A. Maringolo

2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <[hidden email]>:
> 2015-05-29 12:36 GMT-03:00 Tudor Girba <[hidden email]>:
>> Hi,
>>
>> Indeed, this part of the inspector will be revisited for Pharo 5.
>
> Good. I'm sure this can be backported easily ;)
>
>> But, what exactly do you mean by " I just want to select it to run an
>> expression where self refers to the inspected object"?
>
> I have the strong habit of running expressions (it is, send messages)
> to objects directly in the inspector, in the case of the example
> array, I can fiddle selecting the different elements in the array and
> finally select the array itself ("self") to select as the receiver. I
> expect to write these expression on the pane of the right, even when I
> could do it on the pane of the left.
>
> I hope I explained myself. :)
>
>
> Esteban A. Maringolo

www.tudorgirba.com

"Every thing has its own flow"

Ben Coman

Re: Playground inspector and the self variable

In reply to this post by Esteban A. Maringolo

On Sat, May 30, 2015 at 12:15 AM, Esteban A. Maringolo
<[hidden email]> wrote:
> Also... I find myself accidentally closing the whole Playground in an
> attempt to just close the inspector.
>
> I know this is related with me not being the smartest guy in the
> block, but I'm so used to discard inspectors, and when you're somehow
> deep inspecting you completely forgot you started in a "workspace".

But there are other not-smart people ;)
so we should consider your use case
cheers -ben

>
>
>
> Esteban A. Maringolo
>
>
> 2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <[hidden email]>:
>> 2015-05-29 12:36 GMT-03:00 Tudor Girba <[hidden email]>:
>>> Hi,
>>>
>>> Indeed, this part of the inspector will be revisited for Pharo 5.
>>
>> Good. I'm sure this can be backported easily ;)
>>
>>> But, what exactly do you mean by " I just want to select it to run an
>>> expression where self refers to the inspected object"?
>>
>> I have the strong habit of running expressions (it is, send messages)
>> to objects directly in the inspector, in the case of the example
>> array, I can fiddle selecting the different elements in the array and
>> finally select the array itself ("self") to select as the receiver. I
>> expect to write these expression on the pane of the right, even when I
>> could do it on the pane of the left.
>>
>> I hope I explained myself. :)
>>
>>
>> Esteban A. Maringolo
>