Bug 23256 - create search view
Summary: create search view
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-06 04:17 EDT by Gunnar Wagenknecht CLA
Modified: 2019-09-06 15:37 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2002-09-06 04:17:49 EDT
Newer apps all avoid using dialogs for search & replace. It would be a great 
improvement to have the search dialog replaced by a "Search View". You don't 
need to throw away the search dialog. Maybe there could be a preference setting 
to switch between search dialog or search view.
Comment 1 Dani Megert CLA 2003-03-17 05:52:34 EST
You mean integrate the existing dialog into the existing Search view? The
problem here is that plug-in providers can contribute a search page to the
dialog but open/use a totally different Search result view (which can even be
external to the Eclipse workbench window hence reusing a predefined area in the
Search view would not help).

Comment 2 Gunnar Wagenknecht CLA 2003-03-17 15:28:33 EST
I thought of providing the Search dialog from Ctrl+F as a view. But this is a 
very low priority enhancement. I don't thought of putting it into the "Search 
Results" view although it may be possible to display the results underneath the 
search form elements.
Comment 3 Thomas M??der CLA 2004-05-12 04:42:26 EDT
He's talking about the ctrl-f (find) dialog.
Comment 4 Erich Gamma CLA 2004-05-12 09:11:52 EDT
not for 3.0
Comment 5 Dani Megert CLA 2007-06-22 09:59:36 EDT
Get rid of deprecated state.
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:37:09 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.