Well, that is what I am sort of doing. And it turns out to be a kind
of service location.

There are some workarounds, and they are nothing more than just that:
a workaround.

I am letting GIN build all of my presenters, and then I let them bind
the UIs.
Not nice, but that is the way with the fewest dependency lookup calls
for me atm.





On 9 Dez., 16:13, Thomas Broyer <t.bro...@gmail.com> wrote:
> On Dec 9, 12:50 pm, "P.G.Taboada" <pgtabo...@googlemail.com> wrote:
>
>
>
>
>
> > Hi,
>
> > as many other GWT developers I really like the above mentioned
> > approaches.
>
> > I am having a little bit of pain when it comes down to embedding views
> > into views. UiBinder and GIN don't play well together, I am struggling
> > with ugly locator pattern usages to create my sub/ embedded views. My
> > code is now full of //WORKAROUND task tags, hoping to get it solved
> > somehow someday.
>
> > But that is the point: at which direction should I look? MVP tells me
> > to have views injected into my presenter, really nice. UiBinder on the
> > other hand needs the views, would create them properly, but then they
> > would not be available to GIN (compile-time vs. runtime).
>
> > If my feeling is right, we would need some way to hook up into the
> > UIBinder, providing a GIN based MVP resolver, quite similar to the
> > variable resolvers people use in JSF to get hands on Spring beans from
> > JSF. But as far I can see, UiBinder does not provide such extension
> > point.
>
> > Any thoughts here?
>
> How about injecting your "child views" (or Provider<>s) into your view
> and then use @UiField(provided=true) to tell UiBinder you're providing
> those widgets?

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


Reply via email to