[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-search-dev] NewSearchUI vs. SearchUI?
|
bug 65614 filed for the title problem.
Inside the Platform SDK I have only seen some PDE searches come up in Classic Search, but I haven't tried too hard. Let's see... There are references to SearchUI in org.eclipse.help.ide (OpenHelpSearchPageAction), in org.ecliipse.jdt.ui (several places including NLS search), org.eclipse.jdt.ui.examples.javafamily, and org.eclipse.pde.ui. I see some of these have a test for a preference to do an old search vs. a new search so it's not clear which if any would provoke a Classic Search now without some more testing. It would be easier to tell if all the SearchUI references were removed, maybe even deprecated, if that's the direction you want to go in.
Personally I wouldn't mind the two APIs if they would display their results in the same window. I looked at converting my plug-in to NewSearchUI and it's a non-trivial amount of work so I'll have to leave it as it is for now, but it's unfortunate my users will have to juggle two windows, Search and Classic Search.
Perhaps if you want to keep both APIs then under the covers SearchUI could be implemented in terms of NewSearchUI without changing the API? Then you have only one implementation and one window.
-----Original Message-----
From: Thomas Maeder
Sent: Friday, June 04, 2004 3:52 AM
Since we have to maintain backward compatiblility, we still support the "classic" search in 3.0. At this point in time, I'm not aware of the API "rules of engagement" beyond 3.0, So I can't tell you wether the API is ever going away. The idea is, though that the new search API is where you want to be.
> so some searches come up under the "Search" window and some "Classic Search"
that should only be plugin search. Have you seen others come up under "Classic Search"?
> BTW, with recent presentation UI changes, a plug-in I wrote that uses the old SearchUI API now produces an interesting title like this...
sounds like we didn't track changes in the view part API properly. Can you file a bug report?
Thomas
