Some positiveness, One think I like very much with the new GTDebugger: the meaning of each button action from its label is very clear and I am pretty sure beginner with Pharo will understand easily the use of each one.
Regarding productivity, why not using the shortcut described in each button tooltips (the tooltips will deserve a better text than just the repeating of the label, but it is nice there is the shortcut mentioned) Hilaire Le 07/08/2016 à 22:30, Tudor Girba a écrit : > I never explained anyone how they do not understand something :). When I try > to explain something, I mostly try to explain how I reason and the kinds of > constraints I considered so that others can find what is wrong. > > Related to your issue, there is no preference currently. Interestingly, > others have asked for changes for a different layout of the default debugger. > So, we should have a way to allow people to enable/disable debuggers (similar > to how it is for Spotter extensions) and we could then allow people to choose > between different formats for the default debugger. > > I stress “default" because there are others, and this is what my previous > mail actually described (and not breaking the design rules). I did not get a > reply to that mail, so I thought that the description was meaningful enough. > It looks like it was not. > > I opened an issue for this: > https://pharo.fogbugz.com/f/cases/18882/GTDebugger-should-offer-enable-disable-mechanisms-for-extension-debuggers > > Cheers, > Doru > > -- Dr. Geo http://drgeo.eu
