Eclipse Community Forums: Java Development Tools (JDT) » code assistant / imports / documentation

Home » Language IDEs » Java Development Tools (JDT) » code assistant / imports / documentation

code assistant / imports / documentation [message #47480]

Tue, 03 June 2003 11:48

Eclipse User

Hi all

I'm new to eclipse. So far I've been using JBuilder for years.

Is there a way to tell the code assistant (popup with methods) to mark
deprecated methods?
A compiler warning tells me that one of the methods I'm trying to use is
deprected. In JBuilder I had a context menu that allowed me to immediately
open the JavaDoc documentation for the particular class (look up deprecation
hint). How do I do that with eclipse?
Do you know of a plugin that converts
import java.util.List;
import java.util.DateFormat;
style import statements to
import java.util.*;
?

Thanks for your help
Marcel

Re: code assistant / imports / documentation [message #47540 is a reply to message #47480]

Tue, 03 June 2003 12:07

Eclipse User

Originally posted by: faust.acm.org

1st issue: Go to Window->preferences->compiler->problems tab. Change "usage
of deprecated API" option.

2nd issue: Organize imports under Source menu is your friend (Ctrl-Shift-O).
Would you like an unorganize imports option? ;)

Randy

"Marcel St

Re: code assistant / imports / documentation [message #47698 is a reply to message #47540]

Tue, 03 June 2003 13:39

Eclipse User

Thanks for the reply. You didn't really answer my questions, though... ;-)

Randy Faust wrote:
> 1st issue: Go to Window->preferences->compiler->problems tab. Change
> "usage of deprecated API" option.

I don't wanna get rid of the deprecated warning - I want to improve my cody
by replacing the deprected method. eclipse is supposed to help me find the
right method.

> 2nd issue: Organize imports under Source menu is your friend
> (Ctrl-Shift-O). Would you like an unorganize imports option? ;)

I know that option. It's not about beeing organized/sorted or not. I want to
have as little import statements as possible. This can be achieved through
massive use of .* imports.

>> Hi all
>>
>> I'm new to eclipse. So far I've been using JBuilder for years.
>>
>> Is there a way to tell the code assistant (popup with methods) to
>> mark deprecated methods?
>> A compiler warning tells me that one of the methods I'm trying to
>> use is deprected. In JBuilder I had a context menu that allowed me
>> to immediately open the JavaDoc documentation for the particular
>> class (look up deprecation hint). How do I do that with eclipse?
>> Do you know of a plugin that converts
>> import java.util.List;
>> import java.util.DateFormat;
>> style import statements to
>> import java.util.*;
>> ?

Marcel

Re: code assistant / imports / documentation [message #47728 is a reply to message #47698]

Tue, 03 June 2003 14:09

Eclipse User

Well, if you use Ctrl+Space for auto completion, deprecated methods have
a yellow warning sign by them. If you then highlight the method in your
code and press F1, you can select "Javadoc for <method>" to see the javadoc.

"massive use of .* imports" is generally considered a poor practice by
most programmers (see section titled "Import on demand is pure,
unadulterated EVIL" at http://www.javadude.com/tools/importifier/ for
some reasons), so if you want that functionality, you will probably have
to write the plugin yourself.

Marcel Stör wrote:
> Thanks for the reply. You didn't really answer my questions, though... ;-)
>
> Randy Faust wrote:
>
>>1st issue: Go to Window->preferences->compiler->problems tab. Change
>>"usage of deprecated API" option.
>
>
> I don't wanna get rid of the deprecated warning - I want to improve my cody
> by replacing the deprected method. eclipse is supposed to help me find the
> right method.
>
>
>>2nd issue: Organize imports under Source menu is your friend
>>(Ctrl-Shift-O). Would you like an unorganize imports option? ;)
>
>
>
> I know that option. It's not about beeing organized/sorted or not. I want to
> have as little import statements as possible. This can be achieved through
> massive use of .* imports.
>
>
>>>Hi all
>>>
>>>I'm new to eclipse. So far I've been using JBuilder for years.
>>>
>>>Is there a way to tell the code assistant (popup with methods) to
>>>mark deprecated methods?
>>>A compiler warning tells me that one of the methods I'm trying to
>>>use is deprected. In JBuilder I had a context menu that allowed me
>>>to immediately open the JavaDoc documentation for the particular
>>>class (look up deprecation hint). How do I do that with eclipse?
>>>Do you know of a plugin that converts
>>>import java.util.List;
>>>import java.util.DateFormat;
>>>style import statements to
>>>import java.util.*;
>>>?
>>
>
> Marcel
>

Re: code assistant / imports / documentation [message #47760 is a reply to message #47480]

Tue, 03 June 2003 14:06

Eclipse User

Marcel Stör wrote:
> Hi all
>
> I'm new to eclipse. So far I've been using JBuilder for years.
>
> Is there a way to tell the code assistant (popup with methods) to mark
> deprecated methods?

Deprecated methods are marked with an exclamation mark icon in the Code
Assist popup.

> A compiler warning tells me that one of the methods I'm trying to use is
> deprected. In JBuilder I had a context menu that allowed me to immediately
> open the JavaDoc documentation for the particular class (look up deprecation
> hint). How do I do that with eclipse?

Click on the class name and press Shift-F2 (Open External Javadoc).

> Do you know of a plugin that converts
> import java.util.List;
> import java.util.DateFormat;
> style import statements to
> import java.util.*;

Window > Preferences > Java > Organize Imports > "Number of imports
needed for .*".

Hope this helps,

Jeff

Re: code assistant / imports / documentation [message #47849 is a reply to message #47480]

Tue, 03 June 2003 16:50

Eclipse User

> Do you know of a plugin that converts
> import java.util.List;
> import java.util.DateFormat;
> style import statements to
> import java.util.*;
> ?

why would you do that?

first you don't have to be bothered by the imports
because you can use the outline of eclipse that shields
the imports very nicely.

second * imports are very bad things.
You can make code with it that suddenly don't compile anymore
when upgrading to a newer JDK, this should be avoided.

johan

Re: code assistant / imports / documentation [message #48268 is a reply to message #47849]

Wed, 04 June 2003 02:10

Eclipse User

Johan Compagner wrote:
>> Do you know of a plugin that converts
>> import java.util.List;
>> import java.util.DateFormat;
>> style import statements to
>> import java.util.*;
>> ?
>
>
> why would you do that?

Because I hate list of dozens of import statements!

> first you don't have to be bothered by the imports
> because you can use the outline of eclipse that shields
> the imports very nicely.

That sounds real nice! How can I set this up?

> second * imports are very bad things.
> You can make code with it that suddenly don't compile anymore
> when upgrading to a newer JDK, this should be avoided.

Yeah, I'm fully aware of that!

Marcel

Re: code assistant / imports / documentation [message #48471 is a reply to message #47698]

Wed, 04 June 2003 05:32

Eclipse User

Originally posted by: faust.acm.org

I see. So you want a refactoring for replacing deprecated methods. And you'd
like obvious candidates to be offered as replacement suggestions or happen
automatically or something along those lines. Enter a bug report with an
enhancement request.

Randy

"Marcel St

Re: code assistant / imports / documentation [message #49035 is a reply to message #48268]

Wed, 04 June 2003 13:28

Eclipse User

> > first you don't have to be bothered by the imports
> > because you can use the outline of eclipse that shields
> > the imports very nicely.
>
> That sounds real nice! How can I set this up?

Using the Outliner to navigate your source will
make you 'jump' over import statements. There is
also a button in the toolbar which let you 'show the
source of the selected element only' (Tooltip).
So using the outliner makes you 'ignore/hide' the
import part (Its still there but you wont see it that
often).

Currently there is no way to colapse the import
part of a source, but as far as I learned, this is
part of the feature list of Eclipse 3.0 currently in
development.

Hope it was understandable ;)

Martin (Kersten)

Re: code assistant / imports / documentation [message #49182 is a reply to message #48471]

Wed, 04 June 2003 16:58

Eclipse User

AmWed, 4 Jun 2003 11:32:13 +0200, "Randy Faust" <faust@acm.org> wrote:

>I see. So you want a refactoring for replacing deprecated methods. And you'd
>like obvious candidates to be offered as replacement suggestions or happen
>automatically or something along those lines. Enter a bug report with an
>enhancement request.

How should that work? Replacements are often poorly documented.
But sth. like a migration tool with replace all calls of method abc()
for type XYZ with a call efg(), or similar, could be helpful in those
situations.

martin

Re: code assistant / imports / documentation [message #49447 is a reply to message #49182]

Wed, 04 June 2003 19:10

Eclipse User

Originally posted by: faust.acm.org

Agreed, it might be a dubious enhancement. But I can imagine something like
a migration tool which could take advantage of the new refactoring
particpants story to do a refactor rename based on a set of migration rules.

Randy

"Martin M

Previous Topic:	Checkstyle plugins
Next Topic:	Updating The Outline View

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 20:57:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter