I think you just have to try it and see. We're doing that here to determine if UiBinder is a better way of building user interfaces, or if we prefer building UI in a Swing like fashion. There are arguments both ways, but it comes down to taste and preference. UiBinder allows for web designers to be more involved in the creation of GWT applications and in many organizations that's a huge benefit. Another benefit of UiBinder, is that you can use standard HTML elements inside an HTMLPanel to get higher performance as per Kelly Norton's Google I/O talk. Now you can do it in a syntax highlighted, code completion way instead of a Java strings.
-- Arthur Kalmenson On Fri, Dec 11, 2009 at 7:23 AM, Stefan Bachert <[email protected]> wrote: > Classical web development urges me to have a multiple personalities. > That is an disease > I have to deals with > - HTML > - CSS > - JavaScript > - Server-Side calls via AjAx > - Server side implementation in Java or other language > - and references from one to the other > > Thatfor GWT was good to reduce the number of languages. > Everything is Java, CSS could be considered as a designer job making > an other scheme. > No application (=behaviour,functionality) developer should need to > create a CSS > > Now UiBinder comes up with a further XML, and mixing up CSS, HTML and > GWT code. > Somehow I feel be back at the beginning of webdevelopment, and I feel > ill ;-). > > The advantage of declarative programming could be reached in Java in a > much better way. > Look at the following code, it is pure Java and much more declarative > then UiBinder. > It has very less code and is in the end much more flexible since code > could add any rule you like. > > new DialogCreator() > .add(localization.account(), account, 100, DialogCreator.lines > (1)).newLine() > .add(localization.password(), password, 100, DialogCreator.lines > (1)).newLine() > .add(localization.session(), session, 100, DialogCreator.lines > (1)).newLine() > .button(ok) > .button(cancel) > > If you don't like parameters per position, ok, change it to: > > new DialogCreator() > .add(new DialogItem() > .label(localization.account()) > .item(account) > .width(100) > .height(DialogCreator.lines(1)) > ) > .newLine()..... > > What could be done in UiBuilder better/more readable than in java? > What are your thoughts? > > Stefan Bachert > > PS: It is like Spring. IoC could be done in Java itself. Why to deal > with this human unreadable XMLs? > a java compiler is much more flexible and exact as a validation of a > xml (try the check a mispelling of an java class!) > > > PS2: Just to avoid the impression I am just negative. GWT is a great > thing, but surely improvable > > -- > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
