On Thu, Apr 2, 2015 at 9:26 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi Phil,
I think this is just not constructive at all to have a private club like that and not tell us about it.
Please take a look at the reply of Andrei.
I am on 3.0 and there is for sure a ton of fixes in 4.0 already. So, I have to live with what I do have there (e.g. No Spotter yet). Need to vent after having a couple of image freezes when under pressure. Nothing to worry about. Phil
Cheers, Doru
On Thu, Apr 2, 2015 at 6:16 PM, phil@highoctane.be <phil@highoctane.be> 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).
Phil
On Thu, Apr 2, 2015 at 5:30 PM, 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
-- www.tudorgirba.com
"Every thing has its own flow"