Home/IntelliJ IDEA/Compact Create Class Action

Compact Create Class Action

Posted on May 29, 2009 by Peter Gromov

In the upcoming Maia EAP you won’t find separate actions for creating classes, interfaces, enums or @interface anymore. Just one action that does not clutter your desktop — New Java Class.
This does not mean you won’t be able to create interfaces, enums and annotation types, though:

The same functionality will be available for Groovy classes.

#Maia

Comments below can no longer be edited.

8 Responses to Compact Create Class Action

Peter Niederwieser says:
May 29, 2009
Good idea, but maybe there is a better name than Java Class? How about Java Type ?
Leszek says:
June 1, 2009
Thanks for the info. I was a bit surprised when I want to create an enum. Now I see the point 😉
Peter Gromov says:
June 1, 2009
Peter,
We’ve considered ‘Java Type’, but rejected it. It would be a confusing (e.g. ‘create new double[]’) and not easily recognizable by a freshman. And all these Java types we can create are really classes.
Christian Schwanke says:
June 2, 2009
Neat idea 🙂
I like it a lot – the “new” menu can get quite crowded if you have several plugins enabled.
Leszek says:
June 3, 2009
Sorry, byt how can I invoke popup? I;m using Maia 10322 and Tab, Space, Enter, Ctrl+Enter etc. doesn’t work :/

Thanks
Peter Gromov says:
June 4, 2009
Leszek,

It appears like a bug. Is the popup hiding shortly after showing? Do you have Copyright plugin enabled and working? If yes, the fix will be available in the next EAP. Otherwise, please provide more details on what’s happening.
Leszek says:
June 4, 2009
Hi Peter,
I never see this popup and I’m using Copyright plugin. So, thanks for the reply and I’m waiting for the next eap build 😉
Robert Huffman says:
February 1, 2011
I really hate this behavior. There are only a few types of files I create: all the Java file types, groovy occasionally, sometimes a script.

This new behavior means several more key strokes/mouse actions to create, say, a new enumeration. It would be awesome if you could make the old behavior optional, or, better yet, let users configure which types they want in the menu.