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

Bug 87603

Summary:	Log-related views should make use of view linking service
Product:	z_Archived	Reporter:	Curtis d'Entremont <curtispd>
Component:	TPTP.monitoring	Assignee:	Eugene Chan <ewchan>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P1	CC:	ashishp
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	87602
Bug Blocks:

Description Curtis d'Entremont

2005-03-09 20:17:20 EST

Currently some views listen for selection events on other views and make use 
of this information to update their own selections to something related to the 
original selection. For example, if you have the log view and log interactions 
view open at the same time, and select a log record in one of them, the other 
view will automatically update and select that same log record, if it's there.

The problem is that there's no standard way to do this. This feature has been 
requested in bug 87602, and once it is available, the log related views (log 
view, log interactions, log thread interactions) should use it by broadcasting 
their current selection, and updating themselves when the selection changes in 
other views.

Comment 1 Curtis d'Entremont

2005-03-09 20:18:18 EST

Important for higher product.

Comment 2 Ruth Lee

2005-07-12 11:10:42 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 3 Curtis d'Entremont

2005-07-12 13:25:22 EDT

Setting to next release.

Comment 4 Dave Smith

2006-01-25 12:33:38 EST

Setting target to future so it doesn't show up in 4.2 feature query.

Comment 5 Ashish Patel

2007-02-19 12:05:24 EST

In addition, requesting public or provisional access to

org.eclipse.tptp.platform.log.views.internal.LogViewsPlugin
org.eclipse.tptp.platform.log.views.internal.LogViewsMessages
org.eclipse.tptp.platform.log.views.internal.views.LogViewer
org.eclipse.tptp.platform.log.views.internal.util.LogFindCriteria

Comment 6 Curtis d'Entremont

2007-02-19 14:02:49 EST

I would open API requests in a separate enhancement, and try going by use case rather than by existing classes, e.g. I need enough API to be able to do X, Y, and Z.

Comment 7 Alex Nan

2007-08-14 17:15:23 EDT

Due to lack of resources this enhancement request is resolved as WONTFIX. Please feel free to reopen if you consider it's a required enhancement.

Comment 8 Alex Nan

2008-06-24 18:14:15 EDT

Closing.

Comment 9 Paul Slauenwhite

2009-06-30 06:30:59 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).