I see this as being more like refactoring (but it can still be invoked
with optimize imports) because you might want it to be different for
different java files in the same project. For example, images two
classes both have tons of references to Date. In one class, all
references to Date are java.sql except for one to java.util.Date, but in
the other class this situation is swapped. And unlike the current import
settings, I also don't see it as being dynamic because when I'm entering
a FQN I don't want the editor trying to take out the FQN as I type. If I
type it, I want it. If I get some legacy code that is inappropriately
sprinkled with FQN's, I want to run this cleanup.
Jon
Thomas Singer wrote:
> I'm not sure, whether it can be considered a "refactoring". I believe,
> it's just a code layout option.
>
> Tom
>
>
> On Wed, 17 Jul 2002 10:18:15 -0400, Jon Steelman
> <[EMAIL PROTECTED]> wrote:
>
>
>>+1
>>
>>Alternatively, this could be a new refactoring.
>>
>>Jon
>>
>>Igor Karpov wrote:
>>
>>>There is an "optimize imports" functionality that is fine, but what I need is
>>>to convert existing code that uses fully-qualified names for no real reason to
>>>the code with the corresponding import statement and ususal plain names.
>>>
>>>Example
>>>
>>>// Before
>>>
>>>com.abc.Type1 doSomething1() {...}
>>>com.abc.Type2 doSomething2() {...}
>>>com.abc.Type1 doSomething2() {...}
>>>com.abc.Type2 doSomething4() {...}
>>>// a lot..
>>>
>>>// After
>>>
>>>import com.abc.Type1;
>>>import com.abc.Type2;
>>>
>>>Type1 doSomething1() {...}
>>>Type2 doSomething2() {...}
>>>Type1 doSomething2() {...}
>>>Type2 doSomething4() {...}
>>>
>>>So it is the import optimization, isn't it? Would be nice if IDEA supported it.
>>>
>>>
>>>------------------------------------
>>>Mail.Ru - ������, ��������, �������!
>>>------------------------------------
>>
>>
>
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-features
