| Summary: | Search for extenders of abstract classes [search] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | scottstirling |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Jared Burns
The implementors search is for VA/Java compatibility. Why don't you just open the type hierarchy to answer this query. The result is presented in a better way than a search result. It's just a question of workflow and interface consistency. I'm used to looking at an interface, finding no content for the methods, and searching for implementors to find some method content. When I look at an abstract method on an abstract class, my mind is in the same mode - to find the method content, I expect to search for method implementors in the outliner. The advantage of a search is that you can just click on the searches in the search view and it will take you straight to the method you're interested in. With the hierarchy view, I have to find the method in the outliner to bring up the code. to be revisited after 2.0 No plans to provide this for 2.x Would bug 15924 help you ? If I understand Bug 15924 correctly, it boils down to "just use the hierarchy view," which is what Erich originally suggested. This is a valid workaround, but I still think it would be nice to have this functionality with the other search functions. Basically our idea is to improve the hierarchy view instead of improving search since we think the hierarchy is more frequently used. Your examples talk about methods:
>method content, I expect to search for method implementers in the outliner.
Please note that search for implementers is only available for interfaces and
not for members of an interface. Hence to be clear: do you want a search on the
members (which is currently not available even for interfaces) or search for
extenders of the class (as the PR title suggests)?
I'd like search for extenders of a class. The stuff about methods started as an explanation of why I'd like to search for the extenders of a class, but it looks like I got a little carried away. :) Chaning state from assigned later to resolved later. Assigned later got introduced by the last bug conversion and is not a supported Eclipse bug state. I am glad I searched first because I was going to enter an enhancement for exactly this thing. It feels natural to expect to be able to context menu search for subclasses of abstract classes, rather than use the hierarchy View, since I am used to doing it with interfaces and it's essentially the same kind of search. Would I take it as far as searching for extenders of any base class? Maybe not, since a search from java.lang.Object, for example, could yield ridiculous results. But searching for extensions of a *known* base class, i.e., one explicity abstract, is very useful because you often want to know things about abstract classes in a project setting such as: * whether the project (or workspace of related projects) needs the abstract type any more if there are no internally referencing subclasses. * examples of subclasses so you can see how others have used the abstract class. * search for subclasses because you are going to change the abstract class and you want to do an impact analysis on its extensions. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |