Ready to play guinea pig for UI improvements

Hi guys

Many of you may bthink that I'm mad or whatever about new UI elements.
Sometimes this is true :)
but most of the time not. I'm just going straight and (harsh) comments.
So what I propose to the GT team is the following:
     I'm ready to be a guinea pig
     Each time they want I will record a screenflow of my interaction or
perception about new/different tools.
     I will follow a UI debugging  process an expert proposed: talking
aloud about my hypotheses while interacting and
     discovering the tools. I play that in the past with other people
and it works well.

     I encourage other people to do the same to give feeback to GT team.

Stef

Hi,

Yes. That is the type of input that we need.

It would be great if others would do the same.

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"Speaking louder won't make the point worthier."

On 01/22/2016 11:48 AM, Tudor Girba wrote:
> Hi,
>
> Yes. That is the type of input that we need.
>
> It would be great if others would do the same.

Hi Doru,
ok, i often use the debugger to test that some code actually does what i
intended:
in the old one i click first on "stack top" and then click through the
code with "into" and "over" and simply watch the results in "stack top".
with the new debugger "stack top" is gone, in the old one it was
immediately reachable, since it was very much on the top of that small
pane (no scrolling). additionally "into" and "over" became smaller
buttons farther away from the variables section, iow more difficult to
hit while also watching the lower pane. and btw if i do that on tests,
the debugger does not really start at the beginning of the test (also
restart does not help),eg open a debugger in 5.0 on
FFIPluginTests>>testGenericCharCall and do a "restart": you are at the
very end of the test.
werner

Hi,

Thanks. Indeed, we will add stackTop and thisContext back. They were present when we first integrated, but some said they are not useful for them.

> additionally "into" and "over" became smaller buttons farther away from the variables section, iow more difficult to hit while also watching the lower pane. and btw if i do that on tests, the debugger does not really start at the beginning of the test (also restart does not help),eg open a debugger in 5.0 on FFIPluginTests>>testGenericCharCall and do a "restart": you are at the very end of the test.

I do not understand this one. Could you describe more specifically the scenario?

Doru

> werner
>

--
www.tudorgirba.com
www.feenk.com

"From an abstract enough point of view, any two things are similar."

On 01/22/2016 01:16 PM, Tudor Girba wrote:

> I do not understand this one. Could you describe more specifically the scenario?

if i do a "debug test" in the contextmenu of "testGenericCharCall" (in
FFIPluginTests) and press "restart" then "= 130" is highlighted.
werner

On 01/22/2016 01:31 PM, Nicolai Hess wrote:

> I think this is a problem of the way nautilus adds a breakpoint for
> debugging the test.
> (source code and byte code aren't in sync).

ah, i understand
werner

> On 01/22/2016 01:31 PM, Nicolai Hess wrote:
>> I think this is a problem of the way nautilus adds a breakpoint for
>> debugging the test.
>> (source code and byte code aren't in sync).

opened bug report 17455

werner