Talking about drag and drop, it would be great to be able to drag methods
into and out of inner classes in the structure pane, e.g. in the case where
you want to hide an implementation in a delegate private member.

Imagine, you could grab the Group Node corresponding to the interface you
wanted to delegate (which has all the implemented methods below it) and drag
that on to an Inner Class Node - the inner class would be automatically
updated to implement the interface and have the methods added to it and the
implements clause would disappear from the outer class (if applicable).  All
references within the moved code could also be updated (e.g. this ->
OuterClass.this).

Maybe you could do this through a refactoring action too...

Jacques Morel wrote:
> On the same level is the ability to specify where data and functions
> members go in a java file planned for Ariadna (constants, static data
> member, data member, setter&getters, methods,...) Usually I end up
> moving the data member when I generate some code through the IDE. It
> would be nice if IDEA would know where to place them.
> Another way to support this is drag and drop within the IDE. With
> Ctrl-W or code folding it could be a good alternative.
>
> Jacques
> "David Mankin" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
>> +1.  Cut and paste is an annoying work around.  And doesn't work well
>> with folded methods (at least last time I tried).
>>
>> On Thu, 6 Jun 2002, Florin Manolache wrote:
>>
>>> It would be nice to have the possibility to change the methods'
>>> order in a source file.
>>> For example if I have a class Test:
>>>
>>> public class Test {
>>>     public methodA(){}
>>>     public methodB(){}
>>>     public methodC(){}
>>> }
>>>
>>> after moving the methodB "up", the source should look like:
>>>
>>> public class Test {
>>>     public methodB(){}
>>>     public methodA(){}
>>>     public methodC(){}
>>> }
>>>
>>> This can be done for example by enhancing the "File structure"
>>> (Ctrl+F12) popup with the ability to drag methods, or by having 2
>>> buttons with "Move up", "Move down". The same problem for fields,
>>> constructors and nested classes.
>>>
>>> Regards,
>>> Florin
>>>
>>>
>>>
>>> _______________________________________________
>>> Eap-features mailing list
>>> [EMAIL PROTECTED]
>>> http://lists.jetbrains.com/mailman/listinfo/eap-features


_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-features

Reply via email to