The Moldable Debugger - screencasts
Hi, I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser. https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser There is also an older one for announcements (https://vimeo.com/83020584). The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger> Cheers, Andrei
Thanks, Andrei. These are really cool demos! :) Doru On Tue, Dec 31, 2013 at 2:50 PM, Andrei Chis <chisvasileandrei@gmail.com>wrote:
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com "Every thing has its own flow"
Really impressive and useful. Thanks for sharing. Can you point how to install it in a common Pharo 2.0 image? Hernán 2013/12/31 Andrei Chis <chisvasileandrei@gmail.com>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
This only works in Pharo 3.0. Doru On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand < hernan.morales@gmail.com> wrote:
Really impressive and useful. Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis <chisvasileandrei@gmail.com>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584 ).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com "Every thing has its own flow"
How does it load in Pharo 3? As far as I can see the instructions are Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; configuration; load. (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTDebugger) registerExtraToolsOn: Smalltalk tools. (Smalltalk globals at: #GTSUnitDebugger) registerToolsOn: Smalltalk tools. But this fails with #GTDebugger not found in SystemDirectory Thanks On 31/12/2013 18:01, Tudor Girba wrote:
This only works in Pharo 3.0.
Doru
On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand <hernan.morales@gmail.com <mailto:hernan.morales@gmail.com>> wrote:
Really impressive and useful. Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
-- Mark
Thanks for spotting this problem. I renamed a few classes recently. Should be GTGenericStackDebugger instead of GTDebugger The following script should work: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; configuration; load. (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTGenericStackDebugger) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTGenericStackDebugger) registerExtraToolsOn: Smalltalk tools. (Smalltalk globals at: #GTSUnitDebugger) registerToolsOn: Smalltalk tools. On Tue, Dec 31, 2013 at 8:19 PM, Mark Bestley <st@bestley.co.uk> wrote:
How does it load in Pharo 3?
As far as I can see the instructions are Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; configuration; load. (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTDebugger) registerExtraToolsOn: Smalltalk tools. (Smalltalk globals at: #GTSUnitDebugger) registerToolsOn: Smalltalk tools.
But this fails with #GTDebugger not found in SystemDirectory
Thanks
On 31/12/2013 18:01, Tudor Girba wrote:
This only works in Pharo 3.0.
Doru
On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand <hernan.morales@gmail.com <mailto:hernan.morales@gmail.com>> wrote:
Really impressive and useful. Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
-- Mark
On 31/12/2013 18:58, Andrei Chis wrote:
Thanks for spotting this problem. I renamed a few classes recently. Should be GTGenericStackDebugger instead of GTDebugger
The following script should work:
Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; configuration; load. (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTGenericStackDebugger) registerToolsOn: Smalltalk tools. (Smalltalk globals at: #GTGenericStackDebugger) registerExtraToolsOn: Smalltalk tools. (Smalltalk globals at: #GTSUnitDebugger) registerToolsOn: Smalltalk tools.
yes that works Thanks -- Mark
I really like the idea of having debugger adjust to the workflow of the coder, I think the same should apply to Browser too, though AFAIK already Nautilus is very flexible. Congratulations on the videos by the way, they really show the potential of the debugger. I think , and correct me if that is already available, what would be a good idea is a preset system where you could choose between diffirent debugger setups. So a preset for "pettitparser"another for "roassal" etc that means less menus and no need to have separate debuggers :) On Tue, Dec 31, 2013 at 8:01 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
This only works in Pharo 3.0.
Doru
On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand < hernan.morales@gmail.com> wrote:
Really impressive and useful. Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis <chisvasileandrei@gmail.com>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements (https://vimeo.com/83020584 ).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com
"Every thing has its own flow"
On Tue, Dec 31, 2013 at 8:35 PM, kilon alios <kilon.alios@gmail.com> wrote:
I really like the idea of having debugger adjust to the workflow of the coder, I think the same should apply to Browser too, though AFAIK already Nautilus is very flexible.
Congratulations on the videos by the way, they really show the potential of the debugger.
Thanks. I'm glad you liked them.
I think , and correct me if that is already available, what would be a good idea is a preset system where you could choose between diffirent debugger setups. So a preset for "pettitparser"another for "roassal" etc that means less menus and no need to have separate debuggers :)
No, such an option is not available at the moment. One possible problem is that these debuggers were designed to be used only in particular contexts (especially the gui). Trying to use some of them all the time will not result in a nice experience. A setting that could be added is to do the switching automatically. Also, the mechanism to change between debuggers will improve. Right now the quite hidden menu does not tell you that a debugger is available, nor does it make it easy to switch.
On Tue, Dec 31, 2013 at 8:01 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
This only works in Pharo 3.0.
Doru
On Tue, Dec 31, 2013 at 6:57 PM, Hernán Morales Durand < hernan.morales@gmail.com> wrote:
Really impressive and useful. Thanks for sharing.
Can you point how to install it in a common Pharo 2.0 image?
Hernán
2013/12/31 Andrei Chis <chisvasileandrei@gmail.com>
Hi,
I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser.
https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser
There is also an older one for announcements ( https://vimeo.com/83020584).
The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger>
Cheers, Andrei
-- www.tudorgirba.com
"Every thing has its own flow"
On Tue, Dec 31, 2013 at 2:50 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:
https://vimeo.com/83017762 - PetitParser
the petit parser debugger was really a good choice to validate your approach. It's amazing. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
participants (6)
-
Andrei Chis -
Damien Cassou -
Hernán Morales Durand -
kilon alios -
Mark Bestley -
Tudor Girba