Hi, If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons. Do you use this feature? Do we want it in the new debugger? Andrei
On 17 July 2013 15:57, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons.
Do you use this feature? Do we want it in the new debugger?
+1 i want these things to be easily accessible from debugger -1 but i don't like it in form of extra buttons row, which makes debugger UI too bloated.
Andrei
-- Best regards, Igor Stasenko.
On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons.
Do you use this feature?
I don't think so.
Do we want it in the new debugger?
I would not bother⦠things like that are to be removed to gain clarity. Marcus
On Jul 17, 2013, at 4:11 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons.
Do you use this feature?
I don't think so.
In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything. option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before. option 2) Just kill it. Result: the World is a happier place. ;-) But seriously I used that Strategy 2) a lot in the past :-) Marcus
On 17 July 2013 15:18, Marcus Denker <marcus.denker@inria.fr> wrote:
On Jul 17, 2013, at 4:11 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Jul 17, 2013, at 3:58 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons.
Do you use this feature?
I don't think so.
In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything.
option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before.
option 2) Just kill it. Result: the World is a happier place.
;-)
But seriously I used that Strategy 2) a lot in the past :-)
It'll quickly flush out whether or not the feature really is important! frank
Marcus
In general what I learned: You find an obscure, not useful, not used feature in the code base that complexities everything.
option 1) Ask the list. Result: 5 people will suddenly realize that they can not live without that strange feature they never heard about before.
option 2) Just kill it. Result: the World is a happier place.
;-)
But seriously I used that Strategy 2) a lot in the past :-)
Sounds like a good plan :)
I was not even aware that they exist. Stef On Jul 17, 2013, at 3:57 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi,
If the debugging option ExtraDebuggerButtons is set to true a second row containing some actions for browsing code (senders, implementors, versions, etc) will be added under the one with the stepInto, stepOver, etc buttons.
Do you use this feature? Do we want it in the new debugger?
Andrei
participants (5)
-
Andrei Vasile Chis -
Frank Shearar -
Igor Stasenko -
Marcus Denker -
Stéphane Ducasse