When exploring a code, sometimes you end up in a decompiled code from a JAR for which there’s no source code attached. Previously you had to:
A bit too much, isn’t it? Now (in the next EAP) IntelliJ IDEA 11 does it all for you:
By user requests we have added functionality for easy extraction of GSP text to resource bundles. To do this you can select a text fragment, press Alt+Enter and choose the intention “Extract selected text to messages.properties”:
I18nize String dialog will open:
This feature is available in IntelliJ IDEA X #98.231
Now IntelliJ IDEA X is able to debug GSPs. You can set breakpoints and view variable values or evaluate expressions.
As you already know, we are working on GSP editing improvements in IntelliJ IDEA X. In particular, now the editor knows about the variables that the controller supplies to the view.
Example:
Consider an action returning a bookList variable:
And the corresponding GSP file has access to this variable:
Rename, completion and find usages work as they should.
We have added more Grails-specific completion in IntelliJ Idea X. In particular, IntelliJ IDEA now knows about action and controller names in most places where they can appear.
In the ‘controller’ and ‘action’ attributes of some GSP tags:
In some method calls (e.g. redirect(…), render(…), chain(…)):
In the URL mappings configuration:
Needless to say, find usages and rename work for such references as well.
IntelliJ Idea X adds quick navigation for Grails actions and GSP pages. Whenever an action has a same-named view, IDEA creates a gutter icon opposite to the action name. Click that icon and the corresponding page is opened:
As for going back, the GSP editor has a link to the appropriate action at the top:
Tweets about IntelliJ IDEA
