Thursday, May 29, 2014

Re: extend UiBinder engine

Just to answer to what I did, it took me sometime to end up with the wanted feature for diverse GWT restrictions 

Here's the version I'm using on my product

And here's how I use it

Le dimanche 18 mai 2014 22:01:33 UTC+1, Zied Hamdi OneView a écrit :
Hi all,

I have a special need in authorization where I want to control if UiBinder will create or not a widget (I could use visibility visible={roles.admin} in my widgets but I want a smarter solution).

I'd like to use the info in ui:field at template parsing and decide whether the field should be created or not: a central singleton will say if yes or no, that element should be created.

So is there an extension point where I can centrally intercept the internal widget factory?

If the idea is not clear, I'd like to extend a GWT class where I could have a method somehow like

 public  void createWidget( Class widgetClass, Widget parent, String uiField ) 

then rebind the default factory interface with mine in the module definition.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment