Bugzilla – Full Text Bug Listing
| Summary: | Quick Access search should include resources | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Missing name <vp2177> | ||||
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | daniel_megert, Lars.Vogel, loskutov, nobody, psuzzi, pwebster | ||||
| Version: | 4.2 | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 162006 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Missing name
Maybe with a prefix to trigger the text search Search:.... Created attachment 260141 [details]
see the mentioned Open Resource dialog and the Chrome Omnibox custom search
Sounds like an "Open Resource" using quick access like the Chrome Omnibox.
In any case, I have two questions:
1. Are we discussing of a search like the "Open Resource"?
> As example press CTRL+SHIFT+R from the plug-in development perspective.
2. Can you mention some Eclipse plug-in that behaves like Chrome Omnibox?, i.e.
> After typing "Search"+<space> the text shows an indicator meaning the "indexed search" is activated.
(See attached image for details)
(In reply to Missing name from comment #0) > Build Identifier: Juno > > The Quick Access search bar that is now found in Juno should also search > between all the indexed resources of open projects. -1 for that. We already have 'Open Resource' (Ctrl+Shift+R). Plus, there's no reason why 'Quick Access' would find resources but not Java types, for which I search way more often, than for a resource. (In reply to Dani Megert from comment #3) > > The Quick Access search bar that is now found in Juno should also search > > between all the indexed resources of open projects. > > -1 for that. We already have 'Open Resource' (Ctrl+Shift+R). Plus, there's > no reason why 'Quick Access' would find resources but not Java types, for > which I search way more often, than for a resource. Dani, you answer triggered something: why don't we add an extension point for *every* meaningful search embedded into quick access, not just views, commands etc? It is exactly like you've pointed out: if it should find resources, why not Java types? Now let continue the series: if it will include Java types too, why not C++ types? If C++ types, why not XText resources... We at Advantest ship an IDE where the users are working in a 3+ languages environment: Java, C++ and custom XText based languages, all of those have they "special" "open XYZ" buttons or shortcuts. Not only all the dialogs looks differently and there are 3+ different shortcuts: in such mixed environment users don't want to think "which dialog I have to open to see XYZ thing". This is the case where quick access would be of great help, unifying the "simple" search experience. I think there are many similar metaphors to the "extended" Quick Access in other software: the KDE/Gnome/Unity launchers which allow search for almost everything from a single text box. Why shouldn't we do this in IDE too? WDYT? (In reply to Andrey Loskutov from comment #4) > (In reply to Dani Megert from comment #3) > > > The Quick Access search bar that is now found in Juno should also search > > > between all the indexed resources of open projects. > > > > -1 for that. We already have 'Open Resource' (Ctrl+Shift+R). Plus, there's > > no reason why 'Quick Access' would find resources but not Java types, for > > which I search way more often, than for a resource. > > Dani, you answer triggered something: why don't we add an extension point > for *every* meaningful search embedded into quick access, not just views, > commands etc? > > It is exactly like you've pointed out: if it should find resources, why not > Java types? Now let continue the series: if it will include Java types too, > why not C++ types? If C++ types, why not XText resources... > > We at Advantest ship an IDE where the users are working in a 3+ languages > environment: Java, C++ and custom XText based languages, all of those have > they "special" "open XYZ" buttons or shortcuts. Not only all the dialogs > looks differently and there are 3+ different shortcuts: in such mixed > environment users don't want to think "which dialog I have to open to see > XYZ thing". > > This is the case where quick access would be of great help, unifying the > "simple" search experience. I think there are many similar metaphors to the > "extended" Quick Access in other software: the KDE/Gnome/Unity launchers > which allow search for almost everything from a single text box. Why > shouldn't we do this in IDE too? > > WDYT? +1, see bug 162006 which even has a Gerrit change. I started to review it about a year ago. (In reply to Dani Megert from comment #5) > +1, see bug 162006 which even has a Gerrit change. I started to review it > about a year ago. A-ha, I was not aware of this. So this one clearly is the first and best candidate to be implemented together with bug 384307. Removing target milestone for all bugs that are not major or above. > Removing target milestone for all bugs that are not major or above.
Of course I meant "major or below".
Sorry for the noise!
This has been fixed by Mickael. |