Re: [PATCH 1/2] perf tools: Add --tui and --stdio to choose the UI

[Christoph Hellwig]

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


> > 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
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
scrollbars (horizontal / vertical) are a lot more intuitive in a typical
X GUI than in newt.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/