Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 200264

Summary: Improve usability of predefined filtres at profiling
Product: z_Archived Reporter: Alexander N. Alexeev <analexee>
Component: TPTPAssignee: jkubasta
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P2 CC: analexee, chris.l.elford, jkubasta, Mikhail.Voronin, paulslau, sluiman
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
URL: http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_200264.html
Whiteboard: closed471

Description Alexander N. Alexeev CLA 2007-08-16 17:38:29 EDT
Predefined filters which define set of profiled classes should be revisited accordingly for most popular usage scenario. 

Individual predefined filters should be added for several Eclipse projects (set of plugins).
Comment 1 Guru Nagarajan CLA 2007-09-09 18:56:55 EDT
5 PW
Comment 2 Paul Slauenwhite CLA 2007-10-21 21:02:17 EDT
Approved by the AG for TPTP 4.5 with the following comments:

-Requires a documentation sizing.
-How will these filters be used in the statistics views?
-Will this require any UI changes, other than changing the filter sets?
-Filter sets should be reviewed after the design is complete.
Comment 3 Alexander N. Alexeev CLA 2007-10-24 16:23:50 EDT
> -Requires a documentation sizing.
For me it isn't clear, what we can document in this enhancement?

> -How will these filters be used in the statistics views?
I mean take a look at filters which are used in statistical views. But currently seems that update for predefined filters isn't required. 

> -Will this require any UI changes, other than changing the filter sets?
No, this is not planned, only update list of predefined filters. 

> -Filter sets should be reviewed after the design is complete.
I agree, but it can't be done right now.
Main goal of this enhancement is to identify valuable filters and include them to  predefined list, so this is most part of work.

Thanks
Alex.
Comment 4 Paul Slauenwhite CLA 2008-01-17 09:46:45 EST
(In reply to comment #3)

Sorry for the late reply.

> > -Requires a documentation sizing.
> For me it isn't clear, what we can document in this enhancement?

The predefined filters should be documented in the TPTP product documentation so users understand the purpose and rules for each predefined filter.

> > -How will these filters be used in the statistics views?
> I mean take a look at filters which are used in statistical views. But
> currently seems that update for predefined filters isn't required. 

Yes, since the statistics views have been moved to as-is in 4.5.

> > -Filter sets should be reviewed after the design is complete.
> I agree, but it can't be done right now.
> Main goal of this enhancement is to identify valuable filters and include them
> to  predefined list, so this is most part of work.

Lets have a discussion on an AG call once they are complete.
Comment 5 Harm Sluiman CLA 2008-03-24 11:54:55 EDT
This feature isn't going anywhere fast, so how about just providing example filters on the wiki if the situation is not well served by the tools already.

Filter sets could also be provided for download as well, outside the release cycle.

In the end there is not a small set of filters that work for everyone.
Comment 6 Chris Elford CLA 2008-03-31 11:51:22 EDT
this would work.  It could be linked to the proposal for 200499
Comment 7 Kathy Chan CLA 2009-02-23 13:41:16 EST
Mass update of P1 enhancements and defects targetted to future to P2.
Comment 8 Paul Slauenwhite CLA 2009-06-30 06:38:09 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
Comment 9 Paul Slauenwhite CLA 2009-06-30 06:38:33 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
Comment 10 Kathy Chan CLA 2010-11-18 18:56:48 EST
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.