Comments on: Google Releases GWT Designer

By: Hauke

Hauke — Tue, 25 Nov 2014 14:39:43 +0000

It’s dead, Jim.

http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0

GWTDesigner is officially not supported with 2.7 and up (and I didn’t manage to get it to run with 2.6.x also, stayed at 2.5.x for designing).

By: Paul Morris

Paul Morris — Mon, 14 Mar 2011 16:18:27 +0000

Coming from a Flex background (and looking to move over to the AJAX side of things) I was really excited about UIBinder. And although I hardly use the visual editor in Flex/Flash Builder (purist tendencies) I think it’s time I try laying things out visually and see if it speeds up my dev time.

By: San

San — Fri, 25 Feb 2011 18:22:22 +0000

I ve used Google’s Swing Designer… very good , easy and understandable code is generated.. Even the code changes reflect the Gui easily. I think its better than Netbeans Mattisse/GUIBuilder

By: Scott Selikoff

Scott Selikoff — Fri, 25 Feb 2011 18:06:12 +0000

GWT Designer was part of WindowBuilder Pro but the big news is that a lightweight version is now included as part of the GWT 2.2 plugin.

While one could certainly use UiBinder without a visual editor, the advantages of doing so are limited. Most programming languages, such as Flex with MXML for example, that offer such declarative languages, do so with the advantage of being able to edit with a visual tool.

By: Luciano

Luciano — Fri, 25 Feb 2011 15:13:49 +0000

Using UiBinder without a visual editor definitely brings some advantage: defining a UI in Java leads to code that is hard to understand, and UiBinder can create lighter interfaces, since you can mix HTML and widgets.

Also, I’ve never used the GWT Designer, but it existed before UiBinder and can be used to create UIs in pure Java, so it’s not specific to UiBinder.

That said, it makes sense to use a declarative syntax and a visual designer together, although in this case they are not dependent each other.