On Dec 17, 9:25 am, Itzik Yatom itzik...@hotmail.com wrote:
When adding the attribute styleName to an UiBinder XML element, GWT
translates it to setStyleName method call.
The problem is when using a custom Composite class that already has
called to setStyleName method, UiBinder supersedes
Thanks for clearing that up Thomas, I didn't know you could do that
with uibinder!
--
Arthur Kalmenson
On Thu, Dec 17, 2009 at 12:51 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Dec 17, 9:25 am, Itzik Yatom itzik...@hotmail.com wrote:
When adding the attribute styleName to an UiBinder
On 12/17/2009 03:15 PM, Arthur Kalmenson wrote:
Thanks for clearing that up Thomas, I didn't know you could do that
with uibinder!
See
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/test/com/google/gwt/uibinder/test/client/WidgetBasedUi.ui.xml
around line 585
--
You
When adding the attribute styleName to an UiBinder XML element, GWT
translates it to setStyleName method call.
The problem is when using a custom Composite class that already has
called to setStyleName method, UiBinder supersedes the Composite
style.
I wish that UIBinder would call to addStyleName
You could either call addStyleName in the backing Java class, or use a
div around your widget and have multiple CSS classes there. But yes,
as far as I can see, uibinder assumes setsomething for properties on
a widget.
--
Arthur Kalmenson
On Thu, Dec 17, 2009 at 3:25 AM, Itzik Yatom