Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

It looks much better to me, yes. I would need to use it some time before I could give more detailed feedback. (And I can’t really do that until the FFI is fixed, because all my development crashes the VM since I am using Roassal. So I am still on the last Pharo version before the VM switch.) On

Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

Thanks. What do you think of the new solution? Is it sufficient? Doru > On Jan 8, 2016, at 8:05 PM, Johan Fabry wrote: > > > I second Torsten’s comment with regard to the use of space, I also think the > original positioning of stack and code panes is more efficient. > >> On Jan 8, 2016, at

Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

Hi, > On Jan 8, 2016, at 7:28 PM, Torsten Bergmann > wrote: > > Hi, > > with a moldable debugger we should (in the future) be able to support > debugging also different/other programming languages/DSLs in Pharo :) Yes. This would work quite well if the language would pr

Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

Hi, Thanks a lot for the detailed feedback. > On Jan 8, 2016, at 7:28 PM, Torsten Bergmann > wrote: > > Hi, > > with a moldable debugger we should (in the future) be able to support > debugging also different/other programming languages/DSLs in Pharo :) Yes. This would

Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

I second Torsten’s comment with regard to the use of space, I also think the original positioning of stack and code panes is more efficient. > On Jan 8, 2016, at 14:28, Torsten Bergmann wrote: > > Hi, > > with a moldable debugger we should (in the future) be able to support > debugging also d

Re: [Pharo-users] [Pharo-dev] [ann] gtdebugger in pharo 5.0

Hi, with a moldable debugger we should (in the future) be able to support debugging also different/other programming languages/DSLs in Pharo :) - although usually one does necessary have such a use case. So I guess GTInspector or other will be adopted to own needs more than GTDebugger. However: