Feedback on Pharo 1.4 Debugger

classic Classic list List threaded Threaded
2 messages Options
btc btc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Feedback on Pharo 1.4 Debugger

The debugger in Pharo 1.4 is looking very nice - cleaner and easier to
follow.   I wonder if the following might be an additional improvement...

If you consider a class has a method subpart which has a block subpart,
then the "natural flow" of these would continue from left to right.
Referring to [1] - having the "Block" text on the left breaks this sense
of "flow".   What I've drawn in [2] feels more natural to me.

Possible advantages:
* It is easier to see the five SystemReporter items line up.
* Balances brevity with giving a bit of context to distinguish nested
blocks.

[1] NewDebuggerStackView(1).png   (attached)
[2] NewDebuggerStackView(2).png   (attached)

cheers, -ben

NewDebuggerStackView(1).png (70K) Download Attachment
NewDebuggerStackView(2).png (110K) Download Attachment
Eliot Miranda-2 Eliot Miranda-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Feedback on Pharo 1.4 Debugger

Has anybody tried to partially highlight the other shared activations?  i.e. in the below if you selected any of the updateReport activations (home or blocks within it) the other activations could be highlighted in a lighter colour.

On Thu, Feb 9, 2012 at 9:37 AM, Ben Coman <[hidden email]> wrote:
The debugger in Pharo 1.4 is looking very nice - cleaner and easier to follow.   I wonder if the following might be an additional improvement...

If you consider a class has a method subpart which has a block subpart, then the "natural flow" of these would continue from left to right.
Referring to [1] - having the "Block" text on the left breaks this sense of "flow".   What I've drawn in [2] feels more natural to me.

Possible advantages:
* It is easier to see the five SystemReporter items line up.
* Balances brevity with giving a bit of context to distinguish nested blocks.

[1] NewDebuggerStackView(1).png   (attached)
[2] NewDebuggerStackView(2).png   (attached)

cheers, -ben



--
best,
Eliot

Loading...