On Jun 4, 2016 14:11, "Ben Coman" <b...@openinworld.com> wrote: > >> >> >> On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli <g.cote...@gmail.com> >> wrote: >> >>> Hi, >>> I undestand and really liked the idea of a moldable debugger and it's >>> true that the button actions act over the stack, however the decision on >>> what action to use is taken not looking to the stack pane (normally I've >>> decided what to do looking on the source pane). In this context, the >>> buttons are far away where the attention usually is (the code pane). IMHO >>> for the user experience point of view I think is better to have the actions >>> below the stack list and above the stack pane to let the user do not >>> diverge his attention. I'm proposing not dettaching the action buttons for >>> the stack pane, just changing the location (and also moving and inverting >>> the direction of the tab label to not waste space). >>> >> >> Interesting idea. Only the [Stack] tab is a bit lonely over there on the >> right. Perhaps the tab could still be on the left, with the buttons left >> justified against it? >> >> On Sun, Jun 5, 2016 at 1:36 AM, Gabriel Cotelli <g.cote...@gmail.com> wrote:
> Well I put the buttons on the left on purpose because in the case you're > debugging source code the content tends to be on the left half of the > screen. So this keeps the actions close to the decision on what to use. > I do agree. Here is my mockup, dependent on the number of [Stack] tabs expected. cheers -ben
