From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/2] perf tools: Add --tui and --stdio to choose the UI
Date: Sat, 21 Aug 2010 15:26:58 -0300 [thread overview]
Message-ID: <20100821182658.GH2973@ghostprotocols.net> (raw)
In-Reply-To: <20100821174754.GA10213@infradead.org>
Em Sat, Aug 21, 2010 at 01:47:54PM -0400, Christoph Hellwig escreveu:
> On Sat, Aug 21, 2010 at 02:45:11PM -0300, Arnaldo Carvalho de Melo wrote:
> > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > Relying just on ~/.perfconfig or rebuilding the tool disabling support
> > for the TUI is too cumbersome, so allow specifying which UI to use and
> > make the command line switch override whatever is in ~/.perfconfig.
>
> Much better than the current situation, thanks!
>
> I still thinks commands like perf report should not be overloaded for
> two different user interfaces, that is a
>
> perf report
>
> should always be the line oriented interface, and the newt UI should be
> something like
>
> perf treport
>
> Btw, am I the only one that doesn't find the next interface too helpful?
> In general the line oriented interface seem to present the information
> much better, and in the cases where it gets too complicated the newt
Much better how, exactly?
> interface doesn't really helper either. A real gtk/qt interface with
> a proper tree widget would seem like the more useful interface for that.
What would a gtk/qt interface buy us that is not present on the TUI
right now?
I'm not saying it wouldn't buy something, just interested in what is
this something :)
And yes, gtk/qt interfaces should be added. The experience with the TUI
is helping organize the data structures for that.
- Arnaldo
next prev parent reply other threads:[~2010-08-21 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 17:45 [GIT PULL 0/2] perf/core improvements Arnaldo Carvalho de Melo
2010-08-21 17:45 ` [PATCH 1/2] perf tools: Add --tui and --stdio to choose the UI Arnaldo Carvalho de Melo
2010-08-21 17:47 ` Christoph Hellwig
2010-08-21 18:26 ` Arnaldo Carvalho de Melo [this message]
2010-08-22 8:20 ` Christoph Hellwig
2010-08-22 14:11 ` Arnaldo Carvalho de Melo
2010-09-13 17:51 ` [tip:perf/core] perf ui browser: Don't use windows, slang is enough tip-bot for Arnaldo Carvalho de Melo
2010-08-21 17:45 ` [PATCH 2/2] perf tools: add test for strlcpy() Arnaldo Carvalho de Melo
2010-08-21 19:15 ` [GIT PULL 0/2] perf/core improvements Ingo Molnar
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=20100821182658.GH2973@ghostprotocols.net \
--to=acme@infradead.org \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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