[ui-best-practices-working-group] Search UI with results integrated (was

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hi all,

 

it's some time since these discussions were held, but I only found them today.

 

FYI, Wind River has indeed adopted the new APIs put in place in the course

of working on https://bugs.eclipse.org/bugs/show_bug.cgi?id=118200

 

What we currently have is a variant of the Search Results UI in our

commercial products, that lives side-by-side with the classic Eclipse

Search Results UI but can use the search engine. We currently don't

use tweaklets, but have the appearance of the Search Results UI

depend on the kind of search that was made -- just like "Java Search"

and "C++ Search" produce different kind of results in the same Search

Results View, a Wind River Text Search will produce results in the

Search Results View that have the additional UI controls beside it.

 

Our current code is is essentially an evolution of the patches made public

under EPL in bug 118200. See attached for some screenshots.

 

I personally use this every day, and couldn't live without it. There is

some killer features of having the search results integrated with the

controls:

• Ability to change / refine / fix a search very quickly in case there was a typo and the search results are not as expected (see screenshot 1: e.g. change "whole word" match by "regex" match)
• Ability to perform interactive 2nd-stage-filtering on the search results (see screenshot 2) -- results change based on filters just as I apply them.
• Ability to manually remove items from the search results BEFORE a replace operation is made on the remaining items to be replaced -- I can directly preview the matches to take part in replace, select them 1-by-1 and preview what replacement is made (especially helpful if doing Regex backreference replacements -- see screenshot 3).

The evolution that we have made commercially, compared to what's already

attached on the bug, was mostly bug fixes plus minor enhancments such as

color highlighting of matched pattern in the results tree -- so, It's not unlikely

that somebody picking up the patch could come up with similar screenshots

quite easily.

 

We'll happily take part in any discussions when this topic is picked

up again, please keep us in the loop with any work going on in this

direction.

 

Thanks,

--

Martin Oberhuber, Senior Member of Technical Staff, Wind River

Target Management Project Lead, DSDP PMC Member

http://www.eclipse.org/dsdp/tm

> -----Original Message-----
> From: ui-best-practices-working-group-bounces@xxxxxxxxxxx
> [mailto:ui-best-practices-working-group-bounces@xxxxxxxxxxx]
> On Behalf Of Martin Aeschlimann
> Sent: Thursday, July 10, 2008 5:21 PM
> To: User Interface Architecture Working Group
> Subject: RE: [ui-best-practices-working-group] Reminder:
> ConferenceCall: Wednesday, July9th, 17:00 UTC or 10:00 PDT.
> Call 613.287.8000 or 866.362.7064 passcode892048#
>
> Hi,
> there has been various discussion over the years on this
> topic. There was
> even a full implementation ready: see bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=118200
> which adds search controls in the search result UI.
>
> We decided against that proposal in the very last seconds (it
> was available
> in a milestone) for various reasons:
> - Consistency amongst all the contributed search result view.
> Say: Text
> search has a search field in the result view, but Java and
> PDE don't. For
> Java search a simple input field is not enough as there are
> several options
> to be supported and users also rarely enter a search string.
> - Search input field takes space away from search result view
>
> However, as a result from that work we added more APIs so that it's
> possible for search result contributors to contribute result
> views that for
> example are initially shown, not only after the first search.
> WindRiver has a product with their own text search view based on this.
>
> The second proposal discussed was a search field in the trim.
> This is, IMO
> a good idea. We just never had the resources to go in that direction.
>
> Martin Aeschlimann
> Platform Search Committer and former Platform/Search lead.
>
> The current search lead is Daniel Megert.
> We encourage you to file bug with the ideas. (I actually
> think this would
> have the best way to start the discussion right away, as not
> everybody is
> part of the ui-best-practices-working-group)
>
>
>
> |------------>
> | From:      |
> |------------>
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
>   |"Raev, Kaloyan" <kaloyan.raev@xxxxxxx>                    
>                                                              
>                  |
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
> |------------>
> | To:        |
> |------------>
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
>   |"User Interface Architecture Working Group"
> <ui-best-practices-working-group@xxxxxxxxxxx>                
>                                 |
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
> |------------>
> | Date:      |
> |------------>
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
>   |10.07.2008 16:27                                          
>                                                              
>                  |
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
> |------------>
> | Subject:   |
> |------------>
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
>   |RE: [ui-best-practices-working-group] Reminder: Conference
> Call:  Wednesday, July 9th,    17:00 UTC or 10:00 PDT. Call
> 613.287.8000 or    |
>   |866.362.7064 passcode   892048#                           
>                                                              
>                  |
>  
> >-------------------------------------------------------------
> --------------------------------------------------------------
> ---------------|
>
>
>
>
>
> Hello,
>
> Here are my notes from the yesterday's call.
>
> Bogdan Vatkov made a quick walk-through on the pain points in
> the current
> Search UI in Eclipse. The main point is that defining search
> criteria and
> looking at search results are tightly connected tasks.
> Therefore, it is
> quite natural to have them in one and the same view. See the attached
> slides for details.
>
> Kevin McGuire presented a concept that is very close to
> Bogdan's proposal.
> He mentioned that there are dev resources needed to realize this
> experimental search form - may be the interested parties in
> the community
> can help? The Platform team is open on making changes.
>
> There were people on the call that were in favor with the proposed new
> search concept and others that like the existing one. Therefore, the
> following was concluded:
>   - There should be simple and advanced search modes in one
> and the same
> view. User make the choice for the mode.
>   - Eclipse could provide Search UI for both old and new
> concepts and not
> sacrificing any of them.
>
> Action items:
>   - Start with a Bugzilla bug to collect our initial
> resources from this
> walk-through - documents, notes, etc. (Bogdan and Kaloyan)
>   - Bogdan Vatkov will send the presentation slides. (done
> with this mail)
>   - Kevin will send a document describing his new
> experimental search form.
>
>   - Follow-up call in few weeks - there will be more people
> coming back
> from vacation. Until then discussions continue in the mailing list and
> Bugzilla.
>
> Greetings,
> Kaloyan
>
> From: ui-best-practices-working-group-bounces@xxxxxxxxxxx [
> mailto:ui-best-practices-working-group-bounces@xxxxxxxxxxx]
> On Behalf Of
> Bob Fraser
> Sent: Monday, July 07, 2008 11:02 PM
> To: User Interface Architecture Working Group
> Subject: [ui-best-practices-working-group] Reminder: Conference Call:
> Wednesday, July 9th, 17:00 UTC or 10:00 PDT. Call 613.287.8000 or
> 866.362.7064 passcode 892048#
>
> Conference Call: Wednesday, July 9th, 17:00 UTC or 10:00 PDT. Call
> 613.287.8000 or 866.362.7064 passcode 892048#
>
> Agenda: Search UI pain points walkthrough (Bogdan Vatkov)
>
>  - Bob(See attached file: Search_UI_Walkthough.ppt)
> _______________________________________________
> ui-best-practices-working-group mailing list
> ui-best-practices-working-group@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ui-best-practices-wor
king-group
>

Attachment: wr_search1.gif
Description: wr_search1.gif

Attachment: wr_search2.gif
Description: wr_search2.gif

Attachment: wr_search3.gif
Description: wr_search3.gif