Good questions/suggestsion...
The XML approach is very much going backwards in my opinion - it
reminds me of all the legacy web-frameworks - that i have been using
for the last 10 years. Essentially language constructs like "for
loops" and "if/else" are going to have some funky syntax in XML alo
ent APIs that would encourage people to write
> UIs with Java code are less amenable to creating good tools for them. For
> example, the Google Plugin is already working on tools to make editing
> UiBinder templates easy breezy, and we hope other IDEs will do the same.
>
> -
. Fluent APIs that would encourage people to write
> UIs with Java code are less amenable to creating good tools for them. For
> example, the Google Plugin is already working on tools to make editing
> UiBinder templates easy breezy, and we hope other IDEs will do the same.
>
> -
One point I have tried injecting into the GWT community is the
importance of fluent APIs. GWT's Java API is currently quite
cumbersome for layouts and it seems folks immediately jumped to the
conclusion that Java doesn't work and have gone the route of using XML
for layouts. I am not against fol
