I don't believe, that dialogs are that evil. One good example:
class Test {
public Test(String value|) {
}
}
Hit Alt-Enter at the |, press Enter again and you get the following:
class Test {
private String value;
public Test(String value) {
this.value = value;
}
}
But in this dialog (btw, the only Intention action I know) I have the
option for making the variable final -- I make my variables as final
as possible and therefor welcome this option. Does it interrupts your
work flow? Mine is doesn't.
I like dialogs, because if they are well-designed, they could be much
smarter and easier to use than any other solution, including the
"abused" live-templates. And, last but not least, they could provide
options for special wishes (like creating final or static
methods/fields). Even better: IDEA can check before showing the
dialog, whether the method can be made static and grey the option if
needed. Impossible with live-templates.
Tom
On Tue, 18 Jun 2002 10:27:28 +0100, Nathan Brown <[EMAIL PROTECTED]>
wrote:
> I agree, I think dialogs should be avoided wherever possible in a usable ui.
>
> N.
>
> Niels Ull Harremo�s wrote:
> > "Thomas Singer" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]...
> >
> >>I want to be able to define, whether the created method should be
> >>static or the created method/field should be final.
> >>
> >>I only can imagine this using a dialog.
> >
> >
> > I disagree. Having a dialog pop up would interrupt the flow too much. To me,
> > it's much simpler just to write the static/final myself.
> >
> > At least, the dialog popup should be configurable so that the user can
> > disable it. However, that adds yet another configuration item which needs to
> > be documented and understood by the user.
> >
> > Overall, I'd vote no.
> >
> >
> >>Tom
> >
> >
> > Niels Harremo�s
> >
> >
>
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-features
