The current behavior (well, broken in 609 as we all know) for "method-to-be-implemented" is that at the usage point the bulb shows up and the method gets generated upon the user click. While this is OK in many situations, the issue might be *where* the generated method appears.
Often, we'd like to specify ourselves where and when the method goes. (Like if used nested or derived classes) And the other reason: IntelliJ, you probably noticed that we, poor users, are getting addicted to all the Ctrl-SPACE, Ctrl-Shft-SPACE features. So, it would be *very* nice of you to think about providing the Ctrl-SPACE functionality when _implementing_ a new method. Example: public boolean che| <Ctrl-SPACE> would offer a list: checkEverything() - unimplemented from interface Validator checkFirst(int arg1) - possible override from a base class checkSpecial(int arg1, String arg2) - based on unimplemented usage What do you IntelliJ guys think of this? Other IDEA-users opinions? r. P.S. Things are probably not so simple sometimes, e.g. if the methods differ just in arguments. _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
