Hi Jens,
Yeah thanks, I was too tired yesterday (after midnight), I didn't realize I
don't need to use initializer but rather add my code so that I can
dynamically decide whether I want the field to be created or not. I have my
answer thanks. I just thought more poeple had to deal with this
authorization issue and someone surely tried to solve it centrally.
Obviously it's not that common. When I'll have some time for fun I'll do
yet another open source for this purpose :)
thanks anyway
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
