public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 22 Aug 2010 11:11:23 -0300	[thread overview]
Message-ID: <20100822141123.GE19201@ghostprotocols.net> (raw)
In-Reply-To: <20100822082003.GB7365@infradead.org>

Em Sun, Aug 22, 2010 at 04:20:03AM -0400, Christoph Hellwig escreveu:
> On Sat, Aug 21, 2010 at 03:26:58PM -0300, Arnaldo Carvalho de Melo wrote:
> > > 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?

>  - it uses the space available in a terminal window much more
>    efficiently.  Output starts in row 0, column 0 and expands all the
>    way that's needed.
>  - it incluses a descruption of what the columns of output mean
>  - it provides percentages for the individual callchains parts after
>    branching out
>  - in graph/fractal modes there are lines that show how the parts
>    are connected, making it possible to read the output, unlinke
>    the TUI mode where the "expanind" nodes are very hard to follow.
>  - just running perf reports gets an overview of all callchains instead
>    of having to expand dozens of things
>  - the colour scheme is the normal shell one (light gray on black for
>    me) instead of one hurting the eyes

All good points, will work on them, thanks for pointing them out!
 
> 
> > > 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?
> 
> Generally for tree/graph like data structures a real X GUI provides much
> nicer rendering.  It'll allow to render the connected lines just as in
> the line oriented interface, but in a nicer way using real thin lines

Cool, connected lines is something that indeed has to happen, just like
mutt in threaded mode, will work on that.

> in a tree widget.  It'll also genereally allow better text placement
> in the window compared to the single centered window in the newt
> interface.   Also the GUI programs follow the common color scheme of the
> rest of the desktop instead of hurting your eye.  In addition to that

Lets stop hurting eyes!

> scrollbars (horizontal / vertical) are a lot more intuitive in a typical
> X GUI than in newt.

Ok, thanks for the detailed description of the problems.

- Arnaldo

  reply	other threads:[~2010-08-22 14:11 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
2010-08-22  8:20       ` Christoph Hellwig
2010-08-22 14:11         ` Arnaldo Carvalho de Melo [this message]
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=20100822141123.GE19201@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