Re: extend UiBinder engine

Just for other people who will visit this post:

Another less verbose way than you proposed Jens is to use the UiBinder <view:with> functionality with a regular pojo instance, then use

<g:XField visible={roles.admin} />. this lets the view related aspects tied to the view template instead of mixing it in the code logic

This is the approach  I mentioned in the very first mail where I said I wouldn't use that approach

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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.