Is there a plan to have refreshing values in debugger?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Is there a plan to have refreshing values in debugger?

stepharo
Hi

Is there a plan to have refreshed values (instance variables) in
debugger and inspector?
This is super annoying to have to refresh the complete list in the
debugger to see new values
of instance variables.
Why we cannot put back the old pulling behavior and in the future use
reflectivity?

Stef

Reply | Threaded
Open this post in threaded view
|

Re: Is there a plan to have refreshing values in debugger?

Tudor Girba-2
Hi,

The support for polling is available since more than 1 year. The problem is that it is too slow to render the tree using MorphTreeMorph. We wanted to wait until Reflectivity would allow us to capture all objects events, but as that will not happen in Pharo 5, we now want to play with FastTable to see if it would be fast enough.

The issue is here:
https://pharo.fogbugz.com/f/cases/14569/GTInspector-should-do-live-updates-of-objects-and-their-slots

Cheers,
Doru


> On Feb 25, 2016, at 12:47 PM, stepharo <[hidden email]> wrote:
>
> Hi
>
> Is there a plan to have refreshed values (instance variables) in debugger and inspector?
> This is super annoying to have to refresh the complete list in the debugger to see new values
> of instance variables.
> Why we cannot put back the old pulling behavior and in the future use reflectivity?
>
> Stef
>

--
www.tudorgirba.com
www.feenk.com

"Being happy is a matter of choice."





Reply | Threaded
Open this post in threaded view
|

Re: Is there a plan to have refreshing values in debugger?

Marcus Denker-4

> On 25 Feb 2016, at 13:39, Tudor Girba <[hidden email]> wrote:
>
> Hi,
>
> The support for polling is available since more than 1 year. The problem is that it is too slow to render the tree using MorphTreeMorph. We wanted to wait until Reflectivity would allow us to capture all objects events, but as that will not happen in Pharo 5, we now want to play with FastTable to see if it would be fast enough.
>

I am really reluctant to change code for every view… this needs to be tested like crazy before being ready.

And
        -> How to hook into array change?
        -> what about methods already on the stack?

It is not simple… it would need a lot of care.

        Marcus


Reply | Threaded
Open this post in threaded view
|

Re: Is there a plan to have refreshing values in debugger?

stepharo
In reply to this post by Tudor Girba-2


Le 25/2/16 13:39, Tudor Girba a écrit :
>   we now want to play with FastTable to see if it would be fast enough.

I really hope ;)

Stef