Comments on: Excluding Classes from Auto-Import http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/ tips & tricks, news, how-to's Mon, 13 Feb 2012 11:57:49 +0000 http://wordpress.org/?v=2.6.5 By: Shadow http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-194768 Shadow Sat, 01 Oct 2011 01:41:40 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-194768 Oh thank god, I figured it out! Settings -> Editor -> Code Completion -> Preselect the first suggestion: -> Never Oh thank god, I figured it out!

Settings -> Editor -> Code Completion -> Preselect the first suggestion: -> Never

]]> By: Shadow http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-194766 Shadow Sat, 01 Oct 2011 01:40:03 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-194766 How do you turn this irritating thing off?!?!? It is seriously pissing me the f*&k off!!! How do you turn this irritating thing off?!?!?

It is seriously pissing me the f*&k off!!!

]]> By: eyrieowl http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-106073 eyrieowl Tue, 07 Apr 2009 16:46:41 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-106073 This must be the location in the more recent versions. Still on IDEA 7.0.4, and the similar setting is under IDE Settings -> Code Completion. Useful tip, though. This must be the location in the more recent versions. Still on IDEA 7.0.4, and the similar setting is under IDE Settings -> Code Completion. Useful tip, though.

]]> By: Stephen Friedrich http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-103348 Stephen Friedrich Tue, 31 Mar 2009 08:50:02 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-103348 I have agree with Joseph. Me myself I know not to import stuff from com.sun.* However I'd like to forbid that in the project settings. For example some colleagues often manage to import @NotNull from a strange com.sun.* package rather than using the idea annotation. I have agree with Joseph.
Me myself I know not to import stuff from com.sun.*
However I’d like to forbid that in the project settings.
For example some colleagues often manage to import @NotNull from a strange com.sun.* package rather than using the idea annotation.

]]> By: Pat Niemeyer http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-103107 Pat Niemeyer Mon, 30 Mar 2009 19:42:25 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-103107 Yay! java.awt.List is dead, long live java.util.List! Yay! java.awt.List is dead, long live java.util.List!

]]> By: Joseph http://blogs.jetbrains.com/idea/2009/03/excluding-classes-from-auto-import/#comment-103076 Joseph Mon, 30 Mar 2009 18:08:24 +0000 http://blogs.jetbrains.com/idea/?p=585#comment-103076 This is nice but I think it's not smart enough implemented (at least not for IntelliJ's used level :) ): - such a setting should be project/module dependent in first place. (when switching from one project to the other it is ugly to constantly edit those settings) - even more, IntelliJ could be smarter here: e.g. the facets could know what classes they usually don't require, i.e. in a module when a certain facet is active, than it could automatically exclude from completion. Best example I can think of is to exclude the java.awt.* and javax.swing.* classes when having the webmodule active, since many webframeworks also have "TextArea" or "TextFields" , and intelliJ is proposing the AWT/Swing classes in this case. (Also in web modules users work allot with the List interface, and IntelliJ is constantly proposing java.awt.List :) ). It would be also pretty easy to make a Facet/framework incompatibility/improbability matrix, to make IntelliJ behave smarter. This is nice but I think it’s not smart enough implemented (at least not for IntelliJ’s used level :) ):
- such a setting should be project/module dependent in first place.
(when switching from one project to the other it is ugly to constantly edit those settings)
- even more, IntelliJ could be smarter here: e.g. the facets could know what classes they usually don’t require, i.e. in a module when a certain facet is active, than it could automatically exclude from completion.

Best example I can think of is to exclude the java.awt.* and javax.swing.* classes when having the webmodule active, since many webframeworks also have “TextArea” or “TextFields” , and intelliJ is proposing the AWT/Swing classes in this case.
(Also in web modules users work allot with the List interface, and IntelliJ is constantly proposing java.awt.List :) ).
It would be also pretty easy to make a Facet/framework incompatibility/improbability matrix, to make IntelliJ behave smarter.

]]>