I did not know that, thanks On Fri, Apr 3, 2015 at 12:39 PM, Esteban Lorenzano <[email protected]> wrote:
> > On 02 Apr 2015, at 18:16, [email protected] wrote: > > Welcome to the club of GT is awesome and sometimes freezes it all. > > Happened to me once or twice this morning as well. > Switched back to basic inspector for a couple things. > > Having both options available would be nice (like inspect = basic /explore > = gt). > > > you *have* both options > (i) inspect = GT > (I) basic inspect = basic inspect :) > > Esteban > > > Phil > > On Thu, Apr 2, 2015 at 5:30 PM, stepharo <[email protected]> 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 >> >> > > > > > >
