Andrei, Clara, What about integrating the new debugger by default now ? I mean the new debugger is now in Pharo 3.0 alpha but the old debugger is still triggered by default, for example when you do Cmd+Maj+d or when you set the setting 'Always open full debugger'. We (Marcus and I) would like to integrate it now by default in Pharo 3.0 alpha, so we have enough time to stabilize it (in case of problems) and we can then remove the old debugger and old inspectors from Pharo.
Now I want your point of view: - What do you think about integrating the spec debugger by default next week ? - Is it currently stable enough ? - Should I wait a little more so you can add extra features ? Having Andrei's debugger by default requires that it has the full stack menu ready before the Pharo 3.0 release (next spring), because if not people will blame all the Pharo team. - Are you working on it ? - Will it be ready before the next Pharo release ? If you think you need to improve the debugger before we integrate it by default, for example with Clara's GSoC work, please tell me when it will be ready so we can add it into the Pharo 3.0 integration planning. Then I guess you can add a slice with your improvements in the Pharo bug tracker, and I will add an extra slice with smalltalk tools change so the new debugger will be triggered by default. It would be nice if we can integrate it before the end of september. If you think it is ready, I will set the current version by default next week. It is also possible that I integrate the current version by default next week and then later you do a slice with improvements. :) 2013/7/11 Clara Allende <[email protected]> > Great! Thank you guys :) > > > On 11 July 2013 05:17, Andrei Vasile Chis <[email protected]>wrote: > >> >> Actually Erwan Douaille is doing WidgetAbstractWrapper to solve this >>> problem (I've just learnt that a few minutes ago). You may discuss with him >>> about that. >>> >> >> Super. Thanks for all the help and the info >> >> Andrei >> > >
