Bug 45094 - [misc] declarations view should indicate exact range of search results
Summary: [misc] declarations view should indicate exact range of search results
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-17 09:42 EDT by Kai-Uwe Maetzel CLA
Modified: 2006-09-27 07:50 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 Kai-Uwe Maetzel CLA 2003-10-17 09:42:44 EDT
When selecting a Java search result, the exact range of the match should be 
indicated in the declarations view. See #45089 for style of presentation.
Comment 1 Dani Megert CLA 2003-11-13 11:33:54 EST
Code has been prepared so that the SourceView can use the annotation part of the
SourceViewerDecorationSupport.

The goal is to use the normal annotation highlighting. Annotation support is
currently being beefed up so it can be used without with file buffers but this
will not make it into M5.

Once there's an easy way for the SourceView to get the annotation model we
continue on this feature.

Moving target milestone to 3.0 since 3.0 M6 is not available yet (I just ordered
it by the bugzilla maintainer).
Comment 2 Kai-Uwe Maetzel CLA 2003-11-24 05:44:20 EST
Setting mile stone target to M7.
Comment 3 Dani Megert CLA 2004-02-10 07:36:20 EST
Started but not ready for M7.
Comment 4 Dani Megert CLA 2004-03-08 09:33:05 EST
Currently this cannot be done using new search since:
- there's no accessible model for the search results (annotations are created
for the active editor)
- the selection provided by the search view is the real element (e.g. Java
element) and contains no information about the match(es)

Moving to search owner for resolving those problems.
Comment 5 Dirk Baeumer CLA 2004-03-09 03:11:05 EST
Why is the element provided by the search view's selection provider the Java 
element and not a Match element. If it were a match element would this give 
Dani what he needs ?
Comment 6 Dani Megert CLA 2004-03-09 03:33:28 EST
Well, the reason for using the "real" element is probably to prevent all those
little problems that we had when using a wrapper. The wrapper caused/causes
problems when using our menu groups and in cases where adapters aren't supported
it simply does not work. Also, views handling the Search view's selection change
events need to know about the wrapper.
Comment 7 Thomas M??der CLA 2004-03-19 09:06:34 EST
I have added API to access the ISearchResultViewPart to NewSearchUI. From there,
we can get the current ISearchResultPage via getActivePage() and cast (if
appropriate) to a JavaSearchResultPage. This gives us access to the search
result, current match etc.
Comment 8 Dani Megert CLA 2004-03-23 02:27:23 EST
New api came in too late moving to M9
Comment 9 Dani Megert CLA 2004-05-19 09:52:35 EDT
Deferred after 3.0
Comment 10 Dani Megert CLA 2005-04-15 05:27:42 EDT
This was actually a 3.0 plan item. Adapted summary.
Comment 11 Dani Megert CLA 2006-09-27 07:38:21 EDT
Reassigning to inbox since there are currently no plans to work on this.