Selected context specific debugger action

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Selected context specific debugger action

Uko2
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko
Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Tudor Girba-2
You should be able to do that in the GTDebugger (it was made exactly for that).

Doru

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko



--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Uko2
This is cool, but the sad thing is that by default it is not a default tool that Pharoers use.

Uko

On 07 May 2015, at 16:39, Tudor Girba <[hidden email]> wrote:

You should be able to do that in the GTDebugger (it was made exactly for that).

Doru

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko



--

"Every thing has its own flow"

Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Andrei Chis
In reply to this post by Uko2
Where do you want these actions to be placed?
In the menu of the stack or next to the stepInto/Over etc buttons?

Cheers,
Andrei

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko

Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Eliot Miranda-2
In reply to this post by Tudor Girba-2
Hi Tudor,

    could you describe the client-side API and give some examples?  I'm in squeak most if the time so GT is not easily accessible but perhaps the facility could be back ported.  I'd love to have this facility for making the CM simulator easier to step through.

Eliot (phone)

On May 7, 2015, at 7:39 AM, Tudor Girba <[hidden email]> wrote:

You should be able to do that in the GTDebugger (it was made exactly for that).

Doru

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko



--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Uko2
In reply to this post by Andrei Chis
Next to buttons. I want to make an indicator for a selected method.

Buy the way, can you direct me at where should I start to look in GTDebugger. Because I’m quite new with it.

Uko


On 07 May 2015, at 16:58, Andrei Chis <[hidden email]> wrote:

Where do you want these actions to be placed?
In the menu of the stack or next to the stepInto/Over etc buttons?

Cheers,
Andrei

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko


Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Andrei Chis
Then first create a subclass of DebugAction.
Look for example at DoesNotUnderstandDebugAction. There are a lot of subclasses of  DebugAction in the image.
Debugging actions have #appliesToDebugger:. This method controls whether or not the action is loaded by the debugger.
For example DoesNotUnderstandDebugAction is only loaded when the top context is created because of #doesNotUnderstand error.
If you want your action to be present all the time then override #enabled. Look at FullStackDebugAction.

The second step is to load the previous actions in a debugger.
To load them in the SpecDebugger add to the class side a method annotated with <debuggingAction>.
To have them in the gt debugger use <gtDebuggingAction>.
To have them in the pre debug window <preDebuggingAction>.

This cover more or less what's currently available.

Let me know how it goes.

Cheers,
Andrei



On Thu, May 7, 2015 at 6:10 PM, Yuriy Tymchuk <[hidden email]> wrote:
Next to buttons. I want to make an indicator for a selected method.

Buy the way, can you direct me at where should I start to look in GTDebugger. Because I’m quite new with it.

Uko


On 07 May 2015, at 16:58, Andrei Chis <[hidden email]> wrote:

Where do you want these actions to be placed?
In the menu of the stack or next to the stepInto/Over etc buttons?

Cheers,
Andrei

On Thu, May 7, 2015 at 4:36 PM, Yuriy Tymchuk <[hidden email]> wrote:
Hi,

is it possible to have a debugger action specific for selected context? I.e. define label, icon, whether the action is visible depending on the selected context?

Uko



Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Sean P. DeNigris
Administrator
In reply to this post by Uko2
Uko2 wrote
where should I start to look in GTDebugger
Can this be loaded into Pharo, or is is just for Moose?
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Tudor Girba-2
Of course, it can be loaded into Pharo :) (Moose is anyway just some packages loaded into Pharo).

You get it if you load the full GToolkit. Right now, in Pharo you have only GToolkitCore. We load it like this in a Pharo 4 (for now):

Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; 
package: 'ConfigurationOfGTSpotter'; 
package: 'ConfigurationOfGTPlayground'; 
package: 'ConfigurationOfGTInspector'; 
package: 'ConfigurationOfGTInspectorCore'; 
package: 'ConfigurationOfGTPlaygroundCore'; 
load.

Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; 
package: 'ConfigurationOfGlamourCore';
load. 

Gofer new smalltalkhubUser: 'Pharo' project: 'Rubric'; 
package: 'ConfigurationOfRubric'; 
load.

Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; 
configuration;
loadDevelopment

Cheers,
Doru




On Fri, May 8, 2015 at 12:08 AM, Sean P. DeNigris <[hidden email]> wrote:
Uko2 wrote
> where should I start to look in GTDebugger

Can this be loaded into Pharo, or is is just for Moose?



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Selected-context-specific-debugger-action-tp4825049p4825168.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.




--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: Selected context specific debugger action

Sean P. DeNigris
Administrator
Thanks!
Cheers,
Sean