You should do a video because I do not even understand how to use it. So how a newbie can understand?
Stef Le 9/1/16 21:23, Nicolai Hess a écrit :
2016-01-09 20:52 GMT+01:00 Francisco Ortiz Peñaloza <patchi...@gmail.com <mailto:patchi...@gmail.com>>:Hi, i would like to have the GTDebugger in the near future. Great job and thanks! I like the Esteban built instead of the original one and i agree with stef on removing _stack and _thisContext from top and the bytecode view. Aim to simplicity must be a top priority and if anybody needs something more specific can change it easily (its moldable!)I often use thisContext and stackTop for inspecting the current context (I use this a lot when debugging compiler errors) and the stackTop when stepping through cascaded message send, I want to see the intermediate return value.Cheers Francisco On Sat, Jan 9, 2016 at 12:07 PM, Henrik Nergaard <henrik.nerga...@uia.no <mailto:henrik.nerga...@uia.no>> wrote: http://ws.stfx.eu/3KXXDAJ4EUF6 -----Original Message----- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org <mailto:pharo-dev-boun...@lists.pharo.org>] On Behalf Of Stephan Eggermont Sent: Saturday, January 9, 2016 3:36 PM To: pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org> Subject: Re: [Pharo-dev] gtdebugger in pharo 5.0 On 09-01-16 12:39, Dimitris Chloupis wrote: > there has been around a script to automate the screenshots, but > personally I never bother using it because taking a screenshot and > inserting in pillar is the easiest thing. AFAIK the hard part is keeping things up to date. That's where automation helps. Stephan
