Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 59181 - use Context for better user experience
Summary: use Context for better user experience
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eugene Chan CLA
QA Contact:
URL:
Whiteboard: housecleaned460 closed460
Keywords:
Depends on: 83782
Blocks:
  Show dependency tree
 
Reported: 2004-04-19 21:27 EDT by Eugene Chan CLA
Modified: 2016-05-05 10:59 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Chan CLA 2004-04-19 21:27:18 EDT
use Context to provide a better over user experience to have view 
open/close/hide base on user actions in Hyades platform
Comment 1 Valentina Popescu CLA 2005-01-13 22:24:44 EST
Can you add more information
Comment 2 Wayne Ho CLA 2005-01-19 01:03:20 EST
Supporting contexts in the Test Perspective (and possibly the Profiling
Perspective) can support the programmatic opening of views that are relevant to
a given context.

For example, if a specific type of test is selected in the Test Navigator, it
may result in the displaying of a specific view that is only relevant to that
given test.

I'd like to see this Bugzilla re-opened and it's priority increased.  It
probably makes sense to have it assigned specifically for the Test Perspective
first.  It may even be important enough in the Test Perspective to have it
considered for 4.0 and we can follow-up on the exception process... 
Comment 3 Eugene Chan CLA 2005-04-13 11:01:28 EDT
reopen per Wayne's request
Comment 4 Eugene Chan CLA 2005-04-13 11:02:25 EDT
raise priority to P2. 
Valentina, please target feature.
Comment 5 Wayne Ho CLA 2005-04-13 11:06:56 EDT
I have opened a similar enhancement Bug 83782 specifically for the Test
Perspective.  There may be some value in coordinating the efforts across TPTP.
Comment 6 Harm Sluiman CLA 2005-04-14 10:24:54 EDT
move to TPTP for post 3.3 work
Comment 7 Ruth Lee CLA 2005-07-12 10:46:12 EDT
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
Comment 8 Eugene Chan CLA 2006-01-25 15:05:41 EST
Setting target to future so it doesn't show up in 4.2 feature query.
Comment 9 Paul Slauenwhite CLA 2009-06-30 06:39:55 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 Paul Slauenwhite CLA 2009-06-30 06:40:19 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 11 Paul Slauenwhite CLA 2009-06-30 13:28:17 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.
Comment 12 Paul Slauenwhite CLA 2009-06-30 13:51:07 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.