This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Search Results should be opened at bottom like Output window | ||
---|---|---|---|
Product: | utilities | Reporter: | Marian Mirilovic <mmirilovic> |
Component: | Search | Assignee: | Marian Petras <mpetras> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | jrojcek, jskrivanek, pzavadsky |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 10940, 23710 |
Description
Marian Mirilovic
2003-11-13 12:49:29 UTC
Jano, what's your opinion on this? I thought there were two variants possible: document area or standalone dialog. We've found the dialog more useful so implemented it. See issue 36513. I am investigating an option of showing the Search Results in Output area. I hope it would require only the layout changes. I prepared a quick spec for this issue. The spec moves the search results window into the main window. http://ui.netbeans.org/docs/ui/ws/ws_spec-search_results.html Tomas, please let me know what you think about this. Thanks for the spec. If we can't live without having the Search Results inside the main window then the spec is fine. Will require some work to make the Search Results back a TopComponent (furthermore it must be defined in the module layer, must be a singleton and also viewable with no content). But that all is doable. Do you strongly prefer this solution over the dialog? In other words do we have to do it for promo B? So we are going to implement the new spec. Should not be too difficult - the ResultsView component needs to be put back to a TopComponent and the buttons added again to it (instead of being created by DialogDescriptor). We should get rid of using ExplorerPanel which is deprecated and use just plain TopComponent. The details how to abandon ExplorerPanel are described in org.openide.explorer.ExplorerUtils javadoc - it is quite simple, already working e.g. in Component Inspector in form editor. *** Issue 37644 has been marked as a duplicate of this issue. *** *** Issue 37935 has been marked as a duplicate of this issue. *** integrated into the trunk verified in [nb_dev](200401141900) |