Kirk Woll wrote:
>Well, consider what would happen if you declare a class "MyButton" which
>extends "JButton" and you declare an abstract method:
>
>abstract class MyAbstractButton extends JButton {
> abstract void doIt();
>}
>
>Now suppose you extend that class:
>
>class MyConcreteButton extends MyAbstractButton {
>}
>
>With that, the class will not immediately compile since the abstract method
>is unimplemented. Therefore, I hit CTRL-I and choose the one and only
>option available and voila! I am done. If Idea worked as you think it
>should I would be presented with a dialog containing almost 100 methods --
>none of which I am the least bit interested in -- and also the single
>abstract method that I _must_ implement. Which is better behavior?
>
Yep 8) I.e yes there is confusion, but i just drew my point from mere
"extends foo" , "implements foo" notation of Java itself. Not from class
point 8)
But again - i never said that IDEA way to do it has to bee changed 8)
I.e yes i do agree
thats its more convinient.
It also actually more synced with way how compiler reports errors. I.e
abstract methods
will be reported as unimplemented 8)
Cheers,
Sergei
_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list
