Hi,
Currently extending the UI of the debugger is not as easy as extending the
inspector. (It cannot just be done using annotations)
We should work on improving this for Pharo 7.
The actual presentations at the bottom are created
in GTDebuggerVariablesBrowser>>#compose.
To change it in a debugger
Hi
2017-05-15 8:22 GMT+02:00 :
> I've looked at it, but I can't get to reproduce it. I have trouble finding
> an entry point to start understanding.
Starting point is method GTMoldableDebugger>>compose with code:
...
self tabulator with: [:browser |
self
Yeah, in any case, it is not clear what we should do:
- can't we extend the default debugger presentation?
- or should we create a new presentation?
- maybe we can do both, but then we have the question: is there a criteria
to say "if X, extend the default presentation, if Y, create a new
I've looked at it, but I can't get to reproduce it. I have trouble
finding an entry point to start understanding.
Quoting Denis Kudriashov :
Hi.
One possibility is to follow BytecodeDebugger approach. Try to look how it
is implemented
2017-05-12 9:53 GMT+02:00
Hi.
One possibility is to follow BytecodeDebugger approach. Try to look how it
is implemented
2017-05-12 9:53 GMT+02:00 :
> Hello,
>
> I would like to extend the debugger with some context-dependent
> information.
> I am playing with metalinks and I would like to
Hello,
I would like to extend the debugger with some context-dependent information.
I am playing with metalinks and I would like to show, in the debugger,
some information if my metalinks are in the selected method.
This means that:
- I need to add a new presentation in the debugger next to