Yes, we know about this slowness.
It comes from the auto-refresh feature.��
Currently refreshing a tree presentation in Glamour is slow.
We tried to get it faster but I do not think we can do it until the release.

How many people do use this feature?
Should it be enabled by default?
We can add a toggle button in the inspector to enable/disable refresh, per inspector window.



Cheers,
Andrei

On Thu, Apr 2, 2015 at 5:51 PM, Cyril Ferlicot <cyril.ferlicot@gmail.com> wrote:
Yeah.
We was checking the CCMockConfiguration>>#mockProperty for Cocoon and if we go litteral4 -> 1 -> keyword
here that freez a lot.
And if you try to open something else you can put your image on the trash.

On 2 April 2015 at 17:30, stepharo <stepharo@free.fr> wrote:
This morning GTInspector was so slow that it blocked the complete system on the machine of Cyril. :(
We can tell him that he is stupid to have a bad machine or we could try to use this to see how
we can help our users.

So we had to use basicInspect to get our job done (once we ctrl-. to escape the render hell)
because raw uses a tree morph.

Why raw cannot reproduce the old simple and working basicInspect
then we could have a "basic" inspect on double click to avoid to use this bad tree and that we can work.

just try to on RubSmalltalkCodeMode class>>#menuOn: to get the feel. Even on my superfast machine is
is sluggish.

I really think that we should support backdoors.
We need to have a mini browser, a mini debugger and a working inspector.

Setf




--
Cheers
Cyril Ferlicot