Bug 367225 - [mark occurrence][hovering] Wild Card Imports show Dependent Classes in Tool Tip
Summary: [mark occurrence][hovering] Wild Card Imports show Dependent Classes in Tool Tip
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.8   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-12-20 12:32 EST by Nathan Reynolds CLA
Modified: 2011-12-22 11:01 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Reynolds CLA 2011-12-20 12:32:25 EST
Build Identifier: 20110916-0149

Display a tool tip to show the classes that require the import.  For example,
if "import java.util.*;" is moused over, then display "ArrayList, HashMap" in
a vertical list if these classes are used in the Java file.

If I have a bunch of imports at the top and they have wildcards at the end, I
won't know what classes require the import.


Reproducible: Always
Comment 1 Dani Megert CLA 2011-12-21 02:46:46 EST
> If I have a bunch of imports at the top and they have wildcards at the end, I
> won't know what classes require the import.

Why would this information be of any value? Can you give some details? What decisions would you make after seeing that information?
Comment 2 Nathan Reynolds CLA 2011-12-21 11:49:32 EST
(In reply to comment #1)
> Why would this information be of any value? Can you give some details? What
> decisions would you make after seeing that information?

When looking at the imports, I might think "Why is that import there?  What classes am I using from it?".  With the tool tip of information, I might realize that I imported the class from the wrong package.  Or, I might decide that I should use a different class and not create a dependency on a particular library.
Comment 3 Dani Megert CLA 2011-12-22 02:21:51 EST
> Or, I might decide
> that I should use a different class and not create a dependency on a particular
> library.
That you already see from the package name.

Another solution besides the hover could be marking the types when inside the import.
Comment 4 Nathan Reynolds CLA 2011-12-22 11:01:06 EST
(In reply to comment #3)
> Another solution besides the hover could be marking the types when inside the
> import.

Good idea.  Both would be nice.  Just marking the types would require scrolling to find them all in code.