mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Fr?d?ric Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH 0/2] perf newt: Zoom operations
Date: Sun, 4 Apr 2010 21:05:12 +0200	[thread overview]
Message-ID: <20100404190512.GB4564@elte.hu> (raw)
In-Reply-To: <20100404125354.GA3908@ghostprotocols.net>


* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:

> Em Sun, Apr 04, 2010 at 11:58:27AM +0200, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> > > Arnaldo Carvalho de Melo (2):
> > >   perf newt: Add a "Zoom into foo.so DSO" and reverse operations
> > >   perf TUI: Add a "Zoom into COMM(PID) thread" and reverse operations
> > 
> > Pulled, thanks Arnaldo!
> > 
> > There's still a few basic usability glitches that i've noticed:
> > 
> >  - it's not clear how to zoom out, once zoomed in
> 
> I'll use the title line to store the name of the DSO and Thread and the help 
> line to state that to zoom out, press -> + zoom out, and I think that it is 
> a good idea to use 'd' and 'D' to zoom in/out of DSOs and 't' and 'T' to 
> zoom in/out of DSOs.

Cool, a help line will do the trick i'm sure. The only problem situation is 
when there is zero information about how to proceed - some people exit and 
dont ever come back in that case :-)

> >  - there's no help screen and no help line for people to see what can be 
> >    done on a given screen. While it's good that the intuitive things work
> >    by default (arrow keys, escape, enter, etc.), there should also be additional
> >    visual information about what can be done.
> 
> F1 and textboxes with a short description of what can be done given for the 
> first time or till the user presses "Suppress these info boxes" will be 
> added.

Maybe we need 'h' and '?' in addition of F1, as F1 is often already mapped and 
caught by the terminal (it is so with gnome-terminal).

>  
> >  - i think double escape should exit, right now it stays at the 'are you sure'
> >    screen
> 
> Here I thought that something had to be done to avoid that accidentally 
> pressing ESC two times or having "Yes" as default option, trowing away 
> possibly a long processed session, what do others think about it?

Yeah, i think you are right.

> I think that ESC + "Yes" as a default may be ok, as two keys need to be 
> pressed (ESC + Enter), enough warning/confirmation, I gues, right?

Ok, that would work!

Thanks,

	Ingo

  reply	other threads:[~2010-04-04 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04  1:40 Arnaldo Carvalho de Melo
2010-04-04  1:40 ` [PATCH 1/2 v2] perf newt: Add a "Zoom into foo.so DSO" and reverse operations Arnaldo Carvalho de Melo
2010-04-04  1:40 ` [PATCH 2/2] perf TUI: Add a "Zoom into COMM(PID) thread" " Arnaldo Carvalho de Melo
2010-04-04  9:58 ` [PATCH 0/2] perf newt: Zoom operations Ingo Molnar
2010-04-04 12:53   ` Arnaldo Carvalho de Melo
2010-04-04 19:05     ` Ingo Molnar [this message]
2010-04-04 23:20       ` Arnaldo Carvalho de Melo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100404190512.GB4564@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®