This is an excellent news! I have been waiting for that for long! go go go!
Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 8, 2016, at 8:07 AM, Tudor Girba <tu...@tudorgirba.com> wrote: > > Hi, > > We are about to integrate in Pharo a new member of the Glamorous Toolkit: the > GTDebugger. As this is a significant change that might affect your workflow, > here is some background information to help you deal with the change. > > First, you should know that the change is not irreversible and it is easily > possible to disabled the new debugger through a setting. However, please do > take the time to provide us feedback if something does not work out for you. > We want to know what can be improved and we try to react as fast as we can. > > A practical change comes from the fact that the variables are manipulated > through a GTInspector, which makes it cheaper to maintain in the longer run. > > While the first thing that will capture the attention is the default generic > interface, the real power comes from the moldable nature of the debugger. > Like all other GT tools, GTDebugger is also moldable by design. This means > that we can construct custom debuggers for specific libraries at small costs > (often measured in a couple of hundred lines of code). > > For example, the core configuration includes also the SUnit and the bytecode > debugger. These are around 150 lines of code. Here is how the bytecode > debugger looks like: > > <bytecode.png> > > You can find more information in an introductory overview blog post that also > includes some links for further reading: > http://www.humane-assessment.com/blog/gtdebugger-in-pharo/ > <http://www.humane-assessment.com/blog/gtdebugger-in-pharo/> > > Please let us know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > www.feenk.com > > "What is more important: To be happy, or to make happy?" >
