« Resize (tool) windows with keyboard
Live Templates in JavaScript/ActionScript/Flex »

GWT UiBinder support

January 26th, 2010 by Nikolay Chashnikov

The first IntelliJ IDEA 9.0.2 EAP build will add support for UiBinder, new functionality introduced in GWT 2.0. IntelliJ IDEA will understand tags and attributes in ui.xml files:

Inconsistencies between ui.xml file and associated Java class will be highlighted:

You can jump from field to the corresponding tag by using icon on the gutter:

Also IDE provides actions to quickly create new ui.xml file with associated Java class (in Edit | New | Google Web Toolkit menu) and to generate @UiHandler method (in Code | Generate menu).

Expect new version EAP to be published shortly.

Tags: ,

This entry was posted on Tuesday, January 26th, 2010 at 8:03 am and is filed under New Features. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

5 Responses to “GWT UiBinder support”

  1. David Says:
    May 31st, 2010 at 9:36 am

    I have 9.0.2 but this integration doesn’t seem to be working for me. How do I activate it?

    thanks

  2. Nikolay Chashnikov Says:
    June 1st, 2010 at 6:56 am

    Do you have GWT facet in your module?

  3. Jesper Rønn-Jensen Says:
    June 18th, 2010 at 5:14 pm

    While the UiBinder support you describe here works perfectly, there is still one important issue that IntelliJ has yet to support:

    It seems that methods invoked via UiBinders are marked as unused.
    For instance, you have a field declared (in java file):

    @UiBinder
    JespersHyperLink aboutlink;

    And imagine that the JespersHyperLink class has a `setTextAndTitle(String s)` metod. UiBinder syntax allows you to call setters directly from the .ui.xml file on instantiation, which is a good way for me to keep java class size down.

    Unfortunately, the code inspection grays out the metod and postulates it’s unused.

    This is very wrong. Do you have focus on correcting this behaviour?

  4. Alexander Vasiljev Says:
    June 28th, 2010 at 4:51 am

    Hello Jesper.

    If aboutlink is not invoked from Java code, it may still exists in ui.xml (with or without ui:field binding) with setters called there. So aboutlink field is really unused and could be deleted.

  5. Jesper Rønn-Jensen Says:
    November 3rd, 2010 at 3:27 pm

    @Alexander:
    > So aboutlink field is really unused and could be deleted.

    You are right, i could delete @UiField aboutLink in my Java class

    But i think you are missing the point: IntelliJ incrorrectly marks `JespersHyperLink.setTextAndTitle()` as being unused.

    I think that is incorrect: JespersHyperLink.setTextAndTitle() is used in the UiBinder files. So IntelliJ should mark it as used. AND “find usages” should show the usage in uibinder file.

Leave a Reply