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
I fixed it. The latest version should work. Cheers, Andrei On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck <marianopeck@gmail.com
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
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 <chisvasileandrei@gmail.com> wrote:
I fixed it. The latest version should work.
Cheers, Andrei
On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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
On Wed, Dec 2, 2015 at 5:02 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
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 tried loading the latest version of all GTools in Pharo 4 and the image hangs. Luckily if you want you can only load GTDebugger and that should work.
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.
I can make a version of GTDebugger+SUnit extensions that works in pharo 4. Just that version would not get updated any more.
2) Is there a way I can set the GTDebugger as the default debugger and avoid having to click on "Debug Glamorously" ?
GTGenericStackDebugger register.
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).
No problem. I just hope we can get it to work easily as things changed quite a bit. Cheers, Andrei
Thanks in advance,
On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
I fixed it. The latest version should work.
Cheers, Andrei
On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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
On Wed, Dec 2, 2015 at 1:17 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Dec 2, 2015 at 5:02 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
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 tried loading the latest version of all GTools in Pharo 4 and the image hangs. Luckily if you want you can only load GTDebugger and that should work.
I guess the very last version, correct?
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.
I can make a version of GTDebugger+SUnit extensions that works in pharo 4. Just that version would not get updated any more.
That would be awesome :)
2) Is there a way I can set the GTDebugger as the default debugger and avoid having to click on "Debug Glamorously" ?
GTGenericStackDebugger register.
Thanks.
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).
No problem. I just hope we can get it to work easily as things changed quite a bit.
I know. So if at least I am able to use GTDebugger + SUnitExtentions in 4.0 that's enough for me for the moment :) I have no problem loading specific package versions, no problem on loading slices if needed, etc. I just need to know what to load hahaha Cheers,
Andrei
Thanks in advance,
On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
I fixed it. The latest version should work.
Cheers, Andrei
On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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
-- Mariano http://marianopeck.wordpress.com
On Wed, Dec 2, 2015 at 5:34 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
On Wed, Dec 2, 2015 at 1:17 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Dec 2, 2015 at 5:02 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
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 tried loading the latest version of all GTools in Pharo 4 and the image hangs. Luckily if you want you can only load GTDebugger and that should work.
I guess the very last version, correct?
Yes, the latest version.
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.
I can make a version of GTDebugger+SUnit extensions that works in pharo 4. Just that version would not get updated any more.
That would be awesome :)
2) Is there a way I can set the GTDebugger as the default debugger and avoid having to click on "Debug Glamorously" ?
GTGenericStackDebugger register.
Thanks.
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).
No problem. I just hope we can get it to work easily as things changed quite a bit.
I know. So if at least I am able to use GTDebugger + SUnitExtentions in 4.0 that's enough for me for the moment :) I have no problem loading specific package versions, no problem on loading slices if needed, etc. I just need to know what to load hahaha
Cheers,
Andrei
Thanks in advance,
On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis <chisvasileandrei@gmail.com
wrote:
I fixed it. The latest version should work.
Cheers, Andrei
On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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
-- Mariano http://marianopeck.wordpress.com
Hi Andrei, Thanks, it worked. Now, let me ask something else. I do like the #enableStackColoring: feature. And so if that would work with DarkTheme that would be nice. It seems the colors are hardcoded in #textAttributesForStackEntry: right? So if we would want that to be Theme dependent we would have to move that into Theme settings? Just as a temporal fix I made an override of that method with colors that would work more or less with DarkTheme. Thanks! On Wed, Dec 2, 2015 at 1:44 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Dec 2, 2015 at 5:34 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Wed, Dec 2, 2015 at 1:17 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
On Wed, Dec 2, 2015 at 5:02 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
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 tried loading the latest version of all GTools in Pharo 4 and the image hangs. Luckily if you want you can only load GTDebugger and that should work.
I guess the very last version, correct?
Yes, the latest version.
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.
I can make a version of GTDebugger+SUnit extensions that works in pharo 4. Just that version would not get updated any more.
That would be awesome :)
2) Is there a way I can set the GTDebugger as the default debugger and avoid having to click on "Debug Glamorously" ?
GTGenericStackDebugger register.
Thanks.
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).
No problem. I just hope we can get it to work easily as things changed quite a bit.
I know. So if at least I am able to use GTDebugger + SUnitExtentions in 4.0 that's enough for me for the moment :) I have no problem loading specific package versions, no problem on loading slices if needed, etc. I just need to know what to load hahaha
Cheers,
Andrei
Thanks in advance,
On Wed, Dec 2, 2015 at 12:54 PM, Andrei Chis < chisvasileandrei@gmail.com> wrote:
I fixed it. The latest version should work.
Cheers, Andrei
On Wed, Dec 2, 2015 at 4:41 PM, Mariano Martinez Peck < marianopeck@gmail.com> 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
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
participants (2)
-
Andrei Chis -
Mariano Martinez Peck