Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 273872 - [unifyprofiling] Unify user interaction of profiling tools
Summary: [unifyprofiling] Unify user interaction of profiling tools
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: OProfile Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 271425 350195 373014 383263
Blocks:
  Show dependency tree
 
Reported: 2009-04-27 11:15 EDT by Andrew Overholt CLA
Modified: 2022-01-13 14:51 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2009-04-27 11:15:25 EDT
With the gprof contribution (bug #271425), we should look at how we can have one UI with multiple backends.  Let's target this integration at 0.4.
Comment 1 Xavier Raynaud CLA 2009-04-27 11:51:02 EDT
Hi Andrew,

I agree to have, as far as possible, a common look&feel for profiling tools (oprofile, gprof, gcov...).

For info:
1) Even if gcov contribution is not yet submitted, gcov already shares the same look&feel as gprof.

What exactly do you want to unify ?
o Color, fonts & icons ?
o Actions (buttons and mouse actions) ?
o others ?
Comment 2 Andrew Overholt CLA 2009-04-27 11:53:11 EDT
(In reply to comment #1)
> What exactly do you want to unify ?
> o Color, fonts & icons ?
> o Actions (buttons and mouse actions) ?
> o others ?

I was thinking mainly about the general user interaction:  how they launch the profiling, how they do analysis, etc.  The other stuff is definitely important, too!  We can file more specific sub-tasks as we proceed.
Comment 3 Xavier Raynaud CLA 2009-04-27 12:14:06 EDT
(In reply to comment #2)
> (In reply to comment #1)
> > What exactly do you want to unify ?
> > o Color, fonts & icons ?
> > o Actions (buttons and mouse actions) ?
> > o others ?
> 
> I was thinking mainly about the general user interaction:  how they launch the
> profiling, how they do analysis, etc.  The other stuff is definitely important,
> too!  We can file more specific sub-tasks as we proceed.

Ok, I see.

For info, a launch configuration already exists, allowing the user to:
- Display a gmon file
- Run a project, then display the produced gmon file
- Run a project, aggregate produced gmon file in a gmon.sum file, then display result
Unfortunately, this launch config is dedicated to embedded device (it's why it is not included in gprof contribution).

Looking at your comment, it seems you want something similar ?
Comment 4 Andrew Overholt CLA 2009-04-27 12:30:54 EDT
The current workflow for the OProfile plugin is very simple:  a user right-clicks on the binary, the project, or a source file and selects Profile As -> Profile with OProfile.  I would like to see a similar interaction for all profiling tools where possible.  Views specific to various profiling backends will probably still exist but I'd also like to see a common UI where possible (tree view with percentages of execution time, etc.).
Comment 5 Andrew Overholt CLA 2009-11-13 10:52:08 EST
Still important but unclear when someone will get to it.
Comment 6 Alexander Kurtakov CLA 2013-02-19 04:07:27 EST
With 1.2 gcov/gprof can be used with the same workflow as the other tools via the Profliling Tools menu/launchers. I'm closing this bug if there are further issues please open a new one with more details.