That's super cool! But I have a couple of questions: 1) How can I load (exactly) latest working GT (including GT Debugger) for a fresh Pharo 4.0? I need to include this DarkTheme fix and ideally your latest changes to the test runner debugger to see the diff :) Of course, I could use #bleedingEdge but I wonder if at some point that breaks because you assume XXX version work only in Pharo 5.0.
2) Is there a way I can set the GTDebugger as the default debugger and avoid having to click on "Debug Glamorously" ? Sorry to bother in using 4.0 but sometimes when you work in a team, not everybody have the time to move to the bleeding edge of Pharo. I try to keep my client team all working with latest stable release (4.0 in this case). Thanks in advance, On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis <[email protected]> wrote: > I fixed it. The latest version should work. > > Cheers, > Andrei > > On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < > [email protected]> wrote: > >> Hi guys, >> >> I am trying to use GTDebugger in Pharo 4.0 but I find it complicated >> using it with DarkTheme set. It looks like if GTDebugger would not take >> into account some theme settings? I tried in 4.0 and 5.0. >> Look at the attached screenshot. The complicated part is the left pane, >> where the stack is. As you can see, the font is too dark for such a dark >> background. >> >> Also..should GTDebugger work in Pharo 4.0? If true, which version? >> >> Any idea? >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com
