Bug 242235

Summary: Search Criteria and Results integration
Product: [Eclipse Project] Platform Reporter: Bogdan Vatkov <bogdan.vatkov>
Component: SearchAssignee: Platform-Search-Inbox <platform-search-inbox>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, dgaff.eclipse, hristo.sabev, kaloyan, Kevin_McGuire, kpeter, martin.gutschelhofer, mober.at+eclipse, mschorn.eclipse
Version: 3.4   
Target Milestone: ---   
Hardware: All   
OS: All   
URL: http://wiki.eclipse.org/Search_UIWG_Walkthrough
Whiteboard:
Attachments:
Description Flags
Walkthrough slides none

Description Bogdan Vatkov CLA 2008-07-28 09:35:40 EDT
Created attachment 108540 [details]
Walkthrough slides

During a regular meeting of the Eclipse UI Best Practices Working Group I did a walkthrough of the Eclipse Search UI and pointed out an important limitation in the usability of the tooling. Namely the lack of integration (smooth transition) of the Search Criteria (modal dialog) and Search Results (decoupled view).
See the attached presentation.

I am creating this bug entry to track the progress on the topic.
Comment 1 Kaloyan Raev CLA 2008-07-29 04:32:06 EDT
The walkthrough wiki page is created:
http://wiki.eclipse.org/Search_UIWG_Walkthrough

Please, find there meeting minutes and linked resources. 
Comment 2 Martin Oberhuber CLA 2008-07-30 12:02:21 EDT
For text search, see Wind River's search results UI with integrated controls on bug 118200.
Comment 3 Martin Oberhuber CLA 2010-11-05 09:47:38 EDT
Is this related to bug 322721 ?
Comment 4 Hristo Sabev CLA 2010-11-05 10:40:13 EDT
Yes it's related. At least in my oppinion.

The search console is more or less the effort of SAP to overcome some of the problems pointed by Bogdan and Kaloyan.

After few releases inside SAP NetWeaver Developer Studio we decided to contribute the search console to eclipse

(In reply to comment #3)
> Is this related to bug 322721 ?
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:12:12 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.