Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 61305 - Profiling types should be sorted in the list
Summary: Profiling types should be sorted in the list
Status: CLOSED DUPLICATE of bug 61283
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Hyades (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Curtis d'Entremont CLA
QA Contact:
URL:
Whiteboard: closed460
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-06 16:27 EDT by Allan Pratt CLA
Modified: 2012-02-14 16:08 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Pratt CLA 2004-05-06 16:27:26 EDT 
During a demo/review today, it was suggested that the tree of profiling types 
should be sorted somehow - perhaps by name, but what might be even better is to 
sort by "importance" or "likelihood" or something. Perhaps plug-ins could 
specify a sort order value, say from 1 to 100, and if two items have the same 
value they'll be sorted alphabetically. Combined with some documentation 
guidelines, this could be used to group sets of related profiling types 
together while also being flexible enough to handle loose coupling of 
contributors.
Comment 1 Curtis d'Entremont CLA 2004-05-06 16:29:54 EDT 

*** This bug has been marked as a duplicate of 61283 ***
Comment 2 Harm Sluiman CLA 2004-11-03 11:10:13 EST 
house keeping
Comment 3 Paul Slauenwhite CLA 2009-06-30 12:42:16 EDT 
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.