Bugzilla – Full Text Bug Listing
| Summary: | Profiling set dialog tree ordering shouldn't be random | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Curtis d'Entremont <curtispd> |
| Component: | TPTP | Assignee: | amehrega |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | apratt, who |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | housecleaned460 closed471 | ||
| Bug Depends on: | 90754 | ||
| Bug Blocks: | |||
|
Description
Curtis d'Entremont
I notice that when user open an existing configuration. the first one in the list is/are always the selected one(s). *** Bug 61305 has been marked as a duplicate of this bug. *** From Allan: 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. Sorting is now being done alphabetically by name. Although Allan's idea is a good one, a design deficiency on the profiling types API does not allow the addition of a new ordering attribute to dynamic types without breakage. Too risky to do this now, so moving for future consideration. This has been accidentally targeted for 4.0 i2 Moving the target to future since it was not committed for 4.0 Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml Setting to next release. Setting the target to future since it has not officially been planned, but this feature is being considered as part of the JVMTI refactoring. 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). 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). 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. |