6 May
2016
6 May
'16
2:54 p.m.
Hi,
is there some guide / help how to extend the GTDebugger?
I tried to take a look at SUnit/PParser but it looks quite complex…
certainly more complex than extending Inspector. :)
Thanks,
Peter
6 May
6 May
4:23 p.m.
Hi Peter,
Yes, extending the debugger is more work than extending the inspector.
However it depends on what you want to do. Do you need to change the UI of
the debugger or just add new actions?
To create a new UI you need to subclass GTSUnitDebugger and
override debuggerStructureIn: and debuggerTransmissionsIn:. You can the
extend the UI using glamour presentations. On the class side of your UI you
need to implement #defaultTitle, #handlesContext:. If you need to customize
it more you can override at #helpClass, #sessionClass,
#variablesBrowserClass and #availableAutomatically.
To create new actions you need to create subclasses of DebugAction. There
are a lot of examples in the image. To link a action with a UI widget you
need to add to the class side a method that just has an annotation.
Different widgets load actions that have various annotations. For example
the stack widget loads actions annotated with #gtStackDebuggingAction.
Let me know if you need more information to get started. Unfortunately
there isn't a guide that you can use.
Cheers,
Andrei
On Fri, May 6, 2016 at 2:54 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
Hi,
is there some guide / help how to extend the GTDebugger?
I tried to take a look at SUnit/PParser but it looks quite complex…
certainly more complex than extending Inspector. :)
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
7 May
7 May
10:03 a.m.
Hi Andrei,
well I don't know exactly what I want... my initial idea was to quickly
stick something together and see what is available to me and what I can do.
But the overall idea is to extend the debugger to see metalinks-related
info… such as the currently installed metalinks in a method, which one was
called, stepping into and over the metalinks, etc. But I'll start small
with some windows and slowly see where I can go from there.
Also… does the debugger uses regular Glamour? Can I read the Glamour docs
to help me understand it? (I remember reading about Glamour long time ago
and it had things like transmissions and ports… so maybe I can learn the
behavior there.)
Thanks,
Peter
On Fri, May 6, 2016 at 4:23 PM, Andrei Chis <chisvasileandrei(a)gmail.com>
wrote:
Hi Peter,
Yes, extending the debugger is more work than extending the inspector.
However it depends on what you want to do. Do you need to change the UI of
the debugger or just add new actions?
To create a new UI you need to subclass GTSUnitDebugger and
override debuggerStructureIn: and debuggerTransmissionsIn:. You can the
extend the UI using glamour presentations. On the class side of your UI you
need to implement #defaultTitle, #handlesContext:. If you need to customize
it more you can override at #helpClass, #sessionClass,
#variablesBrowserClass and #availableAutomatically.
To create new actions you need to create subclasses of DebugAction. There
are a lot of examples in the image. To link a action with a UI widget you
need to add to the class side a method that just has an annotation.
Different widgets load actions that have various annotations. For example
the stack widget loads actions annotated with #gtStackDebuggingAction.
Let me know if you need more information to get started. Unfortunately
there isn't a guide that you can use.
Cheers,
Andrei
On Fri, May 6, 2016 at 2:54 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
Hi,
is there some guide / help how to extend the GTDebugger?
I tried to take a look at SUnit/PParser but it looks quite complex…
certainly more complex than extending Inspector. :)
Thanks,
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
3159
days inactive
3160
days old
2 comments
2 participants
participants (2)
-
Andrei Chis -
Peter Uhnák