Re: [PATCH v2 5/5] perf report: Initial TUI using newt

[Arnaldo Carvalho de Melo <acme@infradead.org>]

Em Fri, Mar 12, 2010 at 08:01:57AM +0100, Mike Galbraith escreveu:
> On Fri, 2010-03-12 at 07:48 +0100, Mike Galbraith wrote:
> > On Thu, 2010-03-11 at 20:12 -0300, Arnaldo Carvalho de Melo wrote:
> > > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > 
> > 
> > > In this initial patch it just checks if the output is a tty, if not it falls
> > > back to the previous behaviour, also if newt-devel/libnewt-dev is not installed
> > > the previous behaviour is maintaned.
> > > 
> > > Pressing enter on a symbol will annotate it, ESC in the annotation window will
> > > return to the report symbol list.
> > 
> > <build>
> > 
> > Oooooo, major case of happiness.  Nice!
> 
> On the fly event switching ala top in the oven?

Yeah, newt has a FormTimer thing that will exit if the user doesn't
press a key, that will be the time when we refresh the Listbox, etc.
When some key is pressed, we can use the opportunity to switch the
counter or to do annotation, sharing a widget with the report, etc.

Switching perf.data files should be possible, doing diffs using side by
side screens, etc. The widget should allow for N 'perf top' windows, one
per counter, so that we can monitor multiple counters at the same time,
going from live (perf top) to post morten (perf report), doing live
while collecting (perf top + perf record) for later, on another machine,
doing post morten (perf report) also should be possible, etc.

- Arnaldo