UiBinder. How much of standard GWT functionality will it support?

[Konstantin Scheglov]

I'm working now on adding support for simple GWT widgets into
UiBinder support in GWT Designer.
However I see many limitations during this.
For example:

1. Support for TreeItem-s in Tree.
http://code.google.com/p/google-web-toolkit/issues/detail?id=4997

2. Support for "TextBox.textAlignment" property.
http://code.google.com/p/google-web-toolkit/issues/detail?id=4995

3. Support for TabBar and its tabs. How can I add them?

4. NamedFrame support. It has no default constructor, but it is
standard widget, so would be good just allow to specify attribute
"name" and still use only XML to create it.

So, question is - will/should UiBinder support all functionality
available using code, or only part of it can be used declaratively and
rest should be done in Java?

[Mr. Richardson]

Good point I was asking myself something also:

5. FlexTable why can't I make the rows and cells directly.

[Thomas Broyer]

On 13 juin, 14:55, Konstantin Scheglov <konstantin.scheg...@gmail.com>
wrote:

Will it? probably not, unless you send patches to the GWT team.
Should it? I don't think so.

1. TreeItem's in Tree: that'd require a non-negligible amount of work,
and has to be well though out from the beginning. For instance: how
would the XML look like, mixing HTML- and Widget-based TreeItem's? and
allowing custom (subclassed) TreeItem's? IMO, it's probably not worth
the effort.

2. TextBoxBase.TextAlignConstant: this on the other hand looks pretty
easy to fix: a StrictAttributeParser subclass (similar to Horizontal/
VerticalAlignmentConstantParser) that you register in
AttributesParser.

3. TabBar tabs: same issue as with TreeItem's re. HTML vs. Widget; and
a TabBar.Tab also has click and "all key" handlers; should they be
available for use with @UiHandler?

4. NamedFrame: annotating the constructor with @UiConstructor should
be enough.

Proposed by Mr. Richardson:

5. FlexTable (and Grid) rows and cells: that would distract people
from using plain HTML tables. When you cannot use an HTML table, it
generally means you're doing some kind of data binding, which a)
cannot be done in UiBinder anyway and b) means you should probably
switch to the new data widgets which have much better performances.

Let's add a few others:

6. MenuItemSeparator: http://code.google.com/p/google-web-toolkit/issues/detail?id=4883
should be a pretty simple modification of the MenuBarParser

7. custom menu items (MenuItem subclasses):
http://code.google.com/p/google-web-toolkit/issues/detail?id=4550
would probably require a big refactoring of MenuBarParser, but would
fix the above issue at the same time, as MenuItemSeparator is just a
custom MenuItem.

I don't use any of these widgets (well, I use Tree and Grid, but
dynamically populated by data retrieved from the server), so I won't
spend time myself fixing these issue, but some of them are really
simple patches that you could probably do if you think they affect
your business ;-)